[
https://issues.apache.org/jira/browse/HBASE-5547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13398782#comment-13398782
]
Jesse Yates commented on HBASE-5547:
------------------------------------
@Lars: I was thinking that we should have this cleanup thread anyways (similar
to the old logs). I could see moving the ZK stuff to just be monitored from
that thread for what files it should delete or not (less a timeout on file
movement). This would follow the same chaining that we are doing for the
.oldlogs directory.
I don't see it as all that bad to have an async thread from the master that
does the cleanup (and we could remove the synchronous requirement in zk).
I'm +1 on this - its not significantly more overhead than we have already and
notably less overhead than the current implementation. Only downside is that
the current implementation is pretty solid (been using it in my testing for
snapshots and have yet to have a problem).
> 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
> Attachments: hbase-5447-v8.patch, hbase-5447-v8.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
