[
https://issues.apache.org/jira/browse/HBASE-4844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161808#comment-13161808
]
Lars Hofhansl commented on HBASE-4844:
--------------------------------------
@stack: The hooks here would be specific to log rolling. There are already
hooks that are called per log edit.
My thought was that without much tighter integration into the core, there would
be nothing useful the coprocessor hooks could do with the log *files* (can't
move them, delete them, change them, as the rest of the system could not be
altered accordingly to deal with that).
But maybe you're right and the pre hooks should be added as well.
Yes, adding a WALObserver would require a restart of the regionserver(s), there
is no dynamic loading (as far as I can see) for WALObserver, currently.
How do folks backup WALs now? Have some watcher process that watches the .logs
and .oldlogs directory?
> 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
