[
https://issues.apache.org/jira/browse/HBASE-4844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13163975#comment-13163975
]
stack commented on HBASE-4844:
------------------------------
We don't back up WALs.
The logroller could signal new log to copy? Then the copying process could
look in .logs (and in .oldlogs in case it got archived) for the log to copy.
You'd need to add a plugin to logcleaner so master didn't clean the logs from
.oldlogs before it'd been backedup (can we add a generic plugin to the master
that won't delete logs if enabled -- then backup can do the deletes instead).
> Coprocessor hooks for log rolling
> ---------------------------------
>
> Key: HBASE-4844
> URL: https://issues.apache.org/jira/browse/HBASE-4844
> Project: HBase
> Issue Type: New Feature
> Affects Versions: 0.94.0
> Reporter: Lars Hofhansl
> Priority: Minor
>
> In order to eventually do point in time recovery we need a way to reliably
> back up the logs. Rather than adding some hard coded changes, we can provide
> coprocessor hooks and folks can implement their own policies.
--
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
