[
https://issues.apache.org/jira/browse/HBASE-23326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16998370#comment-16998370
]
Sean Busbey commented on HBASE-23326:
-------------------------------------
{quote}
bq. I'll try to get further comments into the context of the doc, but we
absolutely must have archiving for this to go into a branches-2. I've had too
many issues with things that thought they could skip archiving in the last 6
months already.
What's the problem? Need get the WAL back for recovery or debugging?
{quote}
yes, exactly. when something goes wrong there are already well-established ways
for me to get folks to tell hbase to leave stuff alone that's in the archiver
and for things to get cleaned up when we're done.
> Implement a ProcedureStore which stores procedures in a HRegion
> ---------------------------------------------------------------
>
> Key: HBASE-23326
> URL: https://issues.apache.org/jira/browse/HBASE-23326
> Project: HBase
> Issue Type: Improvement
> Components: proc-v2
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Critical
> Fix For: 3.0.0, 2.3.0
>
>
> So we can resue the code in HRegion for persisting the procedures, and also
> the optimized WAL implementation for better performance.
> This requires we merge the hbase-procedure module to hbase-server, which is
> an anti-pattern as we make the hbase-server module more overloaded. But I
> think later we can first try to move the WAL stuff out.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
