[
https://issues.apache.org/jira/browse/HBASE-4844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13487610#comment-13487610
]
Jan Van Besien commented on HBASE-4844:
---------------------------------------
I have never really given the combination of my use case with replication much
thought, but I think they should be orthogonal to each other? Everything that
ends up in the HLog should eventually get replicated and should also eventually
be seen in my coprocessor for my use case.
But your remark made me realize when thinking of failure scenarios that both
the WALActionsListener.postWALWriter and/or the WALObserver.postWALWriter calls
might fail to notify that a HLog file was rolled.
Am I correct that in the replication code, the recovery mechanism to recover
HLog files from failed region servers takes care of this issue?
If so, I think I'll need a similar mechanism in the implementation for my use
case.
Jan
> 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
> Attachments:
> HBASE-4844__postLogRoll_and_postLogArchive_functionality_in_WALObserver.patch
>
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
