[
https://issues.apache.org/jira/browse/HBASE-20700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16505654#comment-16505654
]
Duo Zhang commented on HBASE-20700:
-----------------------------------
Oh for meta there is another problem... The RecoverMetaProcedure will hold the
exclusive lock for the meta table, and since the MRP for meta will hold the
shared lock on meta table so the RecoverMetaProcedure can not be executed...
This is not correct I believe. In SCP we do not hold any table/region lock so
that we are free to execute and then we can fail other RIT procedures to let
our assign procedures go.
For me, the RecoverMetaProcedure is a bit strange. In general, if an RS is
crashed then we will have a SCP for it and if it carries meta then we will
assign meta somewhere else finally. When master start up, we just need to wait
until the RS is online and do not need to mess up the recovery processing...
> Move meta region when server crash can cause the procedure to be stuck
> ----------------------------------------------------------------------
>
> Key: HBASE-20700
> URL: https://issues.apache.org/jira/browse/HBASE-20700
> Project: HBase
> Issue Type: Sub-task
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Attachments: HBASE-20700-UT.patch
>
>
> As said in HBASE-20682.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
