[
https://issues.apache.org/jira/browse/HBASE-20708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16511206#comment-16511206
]
stack commented on HBASE-20708:
-------------------------------
[~uagashe] FYI
Ok. The OPEN Hard-coding then came in with original AMv2 commit. Could try
undoing the hard-coding.
bq. So why not use SCP directly to recover the meta?
IIRC, RMP was trying to be self-contained so easier to reason about... have all
it needed inside itself to get hbase:meta back online; no requirement that we
run another procedure even unto making use of bits of SCP if needbe.
bq. So still the same question, why not use SCP directly? It seems that using
RMP just introduces more complexity......
OK. RMP was intended to do otherwise. If you see more complexity, yeah, lets
fix.
bq. Will write a simple design doc soon.
Thanks. Would be good to step back and go over the permutations apart from code.
Thanks.
> Remove the usage of RecoverMetaProcedure in master startup
> ----------------------------------------------------------
>
> Key: HBASE-20708
> URL: https://issues.apache.org/jira/browse/HBASE-20708
> Project: HBase
> Issue Type: Bug
> Components: proc-v2, Region Assignment
> Reporter: Duo Zhang
> Priority: Blocker
> Fix For: 3.0.0, 2.1.0
>
>
> In HBASE-20700, we make RecoverMetaProcedure use a special lock which is only
> used by RMP to avoid dead lock with MoveRegionProcedure. But we will always
> schedule a RMP when master starting up, so we still need to make sure that
> there is no race between this RMP and other RMPs and SCPs scheduled before
> the master restarts.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
