[
https://issues.apache.org/jira/browse/HBASE-23326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16997902#comment-16997902
]
Michael Stack commented on HBASE-23326:
---------------------------------------
bq. Do you have any ideas which data will be stored in the 'local' HRegion,
besides procedure?
I think we are talking past each other. My suggestion is s/MasterProcs/master/.
A dir named MasterProcs with a region and WALs in it is kinda wonky. If it was
named 'master', you'd know the master was the writer. If master later wants to
use filesystem for data that doesn't fit system tables perhaps because it
needed at startup, this would be natural place for it to put its data beside
the local region and WALs.
bq. I think this can be done in the future, but we need to refactor HRegion
first if we want to do this.
Ok.
bq. ...master carrying table...
This is not going to happen any time soon if at all. It had a bunch of time
spent on it and it couldn't be made work. Will need a bunch of other time spent
redoing startup. I think there other priorities that will come before this
effort.
Suggestion is just get the WALs into existing archive and use its existing
archiving system (rather than have one for data WALs and another for procedure
WALs). We can write another if we have to because someone wants Master to carry
regions.
bq. You can see the code in ProcedureTree for more details.
Sounds good.
Good stuff.
> 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)
