[
https://issues.apache.org/jira/browse/HBASE-9390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758669#comment-13758669
]
Gary Helmling commented on HBASE-9390:
--------------------------------------
.bq we should not allow external clients to control if to recover edits.
Otherwise, HBase data integrity is nondeterministic.
Is this true? If a coprocessor inserts it's own WAL edits to handle state,
wouldn't we want it to also be able to bypass "normal" processing of them on
restore?
Either way, changing the semantics of the RegionObserver API and semantics
seems outside the scope of this issue. Can you open another JIRA if you think
that's really necessary?
> coprocessors observers are not called during a recovery with the new log
> replay algorithm
> -----------------------------------------------------------------------------------------
>
> Key: HBASE-9390
> URL: https://issues.apache.org/jira/browse/HBASE-9390
> Project: HBase
> Issue Type: Bug
> Components: Coprocessors, MTTR
> Affects Versions: 0.95.2
> Reporter: Nicolas Liochon
> Assignee: Jeffrey Zhong
> Attachments: copro.patch, hbase-9390.patch
>
>
> See the patch to reproduce the issue: If we activate log replay we don't have
> the events on WAL restore.
> Pinging [~jeffreyz], we discussed this offline.
--
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
