[
https://issues.apache.org/jira/browse/HBASE-20708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16511180#comment-16511180
]
Duo Zhang commented on HBASE-20708:
-----------------------------------
{quote}
IIRC, thinking was probably that hbase:meta would never be CLOSED.
{quote}
The line of code is committed in HBASE-14614, a very very big patch so I can
not find out the reason... But I do not think that 'hbase:meta would never be
CLOSED', we do have code at client side to deal with meta region not be in OPEN
state. And also, when we move meta region, there could be a time range that
meta is in CLOSED state as no RS takes care of it...
> 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)
