[
https://issues.apache.org/jira/browse/HBASE-20708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16513330#comment-16513330
]
stack commented on HBASE-20708:
-------------------------------
Can I have comment/edit rights on the design doc [~Apache9] please?
bq. Remove RMP ....just use SCP directly to make meta online. .... The code in
RMP will be moved to SCP.
This is a new idea of yours?
I think its good.
If a Master joins a cluster where there is no crashed RS, it just scans meta
and away we go?
We'll add a few steps to SCP -- it'll be a little more involved... but should
be ok.
bq. ....But we still have to wait for meta to be loaded before processing
normal regions in SCP.
We'll still need serverCrashProcessingEnabled type flag to hold up Master
startup until meta is online?
I like this idea too... {{Since a server can only crash once... so queue per
server....}}
> 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
> Assignee: Duo Zhang
> Priority: Blocker
> Fix For: 3.0.0, 2.1.0
>
> Attachments: HBASE-20708-v1.patch, HBASE-20708-v2.patch,
> HBASE-20708-v3.patch, HBASE-20708-v4.patch, HBASE-20708-v5.patch,
> HBASE-20708.patch
>
>
> 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)
