[
https://issues.apache.org/jira/browse/HBASE-20708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang updated HBASE-20708:
------------------------------
Release Note: Introduce an InitMetaProcedure to initialize meta table for a
new HBase deploy. Marked RecoverMetaProcedure deprecated and remove the usage
of it in the current code base. We still need to keep it in place for
compatibility. The code in RecoverMetaProcedure has been moved to
ServerCrashProcedure, and SCP will always be enabled and we will rely on it to
bring meta region online.
> 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-v6.patch, HBASE-20708-v7.patch, HBASE-20708-v8.patch,
> HBASE-20708-v9.patch, HBASE-20708-v9.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.
> Please see [#[accompanying design document
> |https://docs.google.com/document/d/1_872oHzrhJq4ck7f6zmp1J--zMhsIFvXSZyX1Mxg5MA/edit#heading=h.xy1z4alsq7uy]
> ]where we call out the problem being addressed by this issue in more detail
> and in which we describe our new approach to Master startup.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
