Blocker Description
Currently, incremental backup is based on WAL files. Bulk data loading bypasses WALs for obvious reasons, breaking incremental backups. The only way to continue backups after bulk loading is to create new full backup of a table. This may not be feasible for customers who do bulk loading regularly (say, every day).
Here is the review board (out of date):
https://reviews.apache.org/r/54258/
In order not to miss the hfiles which are loaded into region directories in a situation where postBulkLoadHFile() hook is not called (bulk load being interrupted), we record hfile names thru preCommitStoreFile() hook.
At time of incremental backup, we check the presence of such hfiles. If they are present, they become part of the incremental backup image.
Here is review board:
https://reviews.apache.org/r/57790/
Google doc for design:
https://docs.google.com/document/d/1ACCLsecHDvzVSasORgqqRNrloGx4mNYIbvAU7lq5lJE
Attachments
Attachments
Issue Links
- incorporates
-
HBASE-18843 Add DistCp support to incremental backup with bulk loading
-
- Resolved
-
- is part of
-
HBASE-14414 HBase Backup/Restore Phase 3
-
- Closed
-