[
https://issues.apache.org/jira/browse/HBASE-5547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13241018#comment-13241018
]
Jesse Yates commented on HBASE-5547:
------------------------------------
Implementation consideration: should we be backing up _all_ deletes or just
those that are system enabled. For instance, we could delete a table via the
api/shell. However, that is a pointed act and probably doesn't mean we want to
back that data up. Proposing we keep it simple FTM and just backup system
removed HFiles. Otherwise, we keep around tons of copies of files.
Alternative I wouldn't mind (but increases the size of the patch and feels like
scope creep) would be to backup even for table level deletes and on things like
deleting a table, you need a bool to specify "but not the backup".
thoughts?
> 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
