[
https://issues.apache.org/jira/browse/HBASE-20708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16507893#comment-16507893
]
Duo Zhang commented on HBASE-20708:
-----------------------------------
So when startup, we will first go to zookeeper to ask for the location of the
meta region, and then check whether the region server is still online, if not,
will try to schedule a SCP for it, of course we need to check whether there is
already a SCP for it. And then we start everything else. And for SCP it will
not schedule an RMP for recover meta, just include the logic in RMP to its own
code.
> 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)
