[
https://issues.apache.org/jira/browse/HBASE-5547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13245952#comment-13245952
]
[email protected] commented on HBASE-5547:
------------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/4633/
-----------------------------------------------------------
Review request for hbase, Michael Stack and Lars Hofhansl.
Summary
-------
Essentially, whenever an hfile would be deleted, it is instead moved to the
archive directory. In this impl, the archive directory is on a per table basis,
but defaults to '.archive'. Removing hfiles occurs in three places -
compaction, merge and catalog janitor. The former and two latter are distinctly
different code paths, but but did pull out some similarities. The latter two
end up calling the same method, so there should be a reasonable amount of
overlap.
Implementation wise:
Updated the HMasterInterface to pass the calls onto the zookeeper.
Added a zk listener to handle updates from the master to the RS to backup.
Added a utility for removing files and finding archive directories
Added tests for the regionserver and catalogjanitor approaches.
Added creation of manager in regionserver.
This addresses bug HBASE-5547.
https://issues.apache.org/jira/browse/HBASE-5547
Diffs
-----
src/main/java/org/apache/hadoop/hbase/HConstants.java 21ac4ba
src/main/java/org/apache/hadoop/hbase/client/HBaseAdmin.java 16e4017
src/main/java/org/apache/hadoop/hbase/ipc/HMasterInterface.java ea7ae45
src/main/java/org/apache/hadoop/hbase/master/CatalogJanitor.java 79d5fdd
src/main/java/org/apache/hadoop/hbase/master/HMaster.java 9bd4ace
src/main/java/org/apache/hadoop/hbase/regionserver/HFileArchiveManager.java
PRE-CREATION
src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java 1d11f8f
src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java 4f80999
src/main/java/org/apache/hadoop/hbase/regionserver/RegionServerServices.java
6884d53
src/main/java/org/apache/hadoop/hbase/regionserver/Store.java 0c7b396
src/main/java/org/apache/hadoop/hbase/util/HFileArchiveUtil.java PRE-CREATION
src/main/java/org/apache/hadoop/hbase/zookeeper/HFileArchiveTracker.java
PRE-CREATION
src/main/java/org/apache/hadoop/hbase/zookeeper/ZooKeeperWatcher.java 0f83655
src/main/resources/hbase-default.xml 341431a
src/test/java/org/apache/hadoop/hbase/master/MockRegionServer.java d2b3060
src/test/java/org/apache/hadoop/hbase/master/TestCatalogJanitor.java 227c5f2
src/test/java/org/apache/hadoop/hbase/regionserver/TestRegionHFileArchiving.java
PRE-CREATION
src/test/java/org/apache/hadoop/hbase/util/MockRegionServerServices.java
bb3ddd7
Diff: https://reviews.apache.org/r/4633/diff
Testing
-------
Added two tests for the separate cases - archiving via the regionserver and for
the catalog tracker. Former runs in a mini cluster and also touches the changes
to HMasterInterface and zookeeper.
Thanks,
Jesse
> Don't delete HFiles when in "backup mode"
> -----------------------------------------
>
> Key: HBASE-5547
> URL: https://issues.apache.org/jira/browse/HBASE-5547
> Project: HBase
> Issue Type: New Feature
> Reporter: Lars Hofhansl
> Assignee: Jesse Yates
>
> This came up in a discussion I had with Stack.
> It would be nice if HBase could be notified that a backup is in progress (via
> a znode for example) and in that case either:
> 1. rename HFiles to be delete to <file>.bck
> 2. rename the HFiles into a special directory
> 3. rename them to a general trash directory (which would not need to be tied
> to backup mode).
> That way it should be able to get a consistent backup based on HFiles (HDFS
> snapshots or hard links would be better options here, but we do not have
> those).
> #1 makes cleanup a bit harder.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
