[
https://issues.apache.org/jira/browse/HBASE-4132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13070825#comment-13070825
]
Gary Helmling commented on HBASE-4132:
--------------------------------------
Hmm, this seems to be a confusion of
{{org.apache.hadoop.hbase.regionserver.wal.WALObserver}} and
{{org.apache.hadoop.hbase.coprocessor.WALObserver}}. Not surprising since both
classes have the same name. I think the former is the "WAL listener" used in
replication and the latter is the coprocessor interface for WALs. I know the
former has been around longer, but maybe we should consider renaming it to
WALListener. Or maybe we should bite the bullet and combine these two
interfaces to one. (I say that knowing very little about replication and
whether it would make sense/be feasible to convert it to a coprocessor
implementation).
Anyway, I see no problem adding {{pre/postArchiveStart}} and
{{pre/postArchiveCompleted}} to
{{org.apache.hadoop.hbase.coprocessor.WALObserver}}, as Andy mentions. Would
that be sufficient, or should we look at adding the logRoll and logClose events
from {{o.a.h.h.regionserver.wal.WALObserver}} as well?
> Extend the WALObserver API to accomodate log archival
> -----------------------------------------------------
>
> Key: HBASE-4132
> URL: https://issues.apache.org/jira/browse/HBASE-4132
> Project: HBase
> Issue Type: Improvement
> Components: regionserver
> Reporter: dhruba borthakur
> Assignee: dhruba borthakur
> Fix For: 0.92.0
>
> Attachments: walArchive.txt
>
>
> The WALObserver interface exposes the log roll events. It would be nice to
> extend it to accomodate log archival events as well.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
