[
https://issues.apache.org/jira/browse/HBASE-5547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse Yates updated HBASE-5547:
-------------------------------
Release Note:
All HFiles are now automatically archived to the configured
"hbase.table.archive.directory". HFiles are cleaned similarly to HLogs - a
cleaner delegate chain that is instantiated as per the configured classes.
Similar to hlog cleaners, a TimeToLiveHFileCleaner is used by default, and
specified under the "hbase.master.hfilecleaner.plugins" configuration key.
In unifying the two cleaner interfaces, the new configuration parameter to use
the TimeToLiveHLogCleaner is:
<property>
<name>hbase.master.logcleaner.plugins</name>
<value>org.apache.hadoop.hbase.master.cleaner.TimeToLiveLogCleaner</value>
</property>
It is still enabled by default, so nothing needs to be changed if you are not
modifying the logcleaners.
> 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
> Fix For: 0.94.2
>
> Attachments: 5547-v12.txt, hbase-5447-v8.patch, hbase-5447-v8.patch,
> hbase-5547-v9.patch, java_HBASE-5547_v13.patch, java_HBASE-5547_v4.patch,
> java_HBASE-5547_v5.patch, java_HBASE-5547_v6.patch, java_HBASE-5547_v7.patch
>
>
> 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
