[
https://issues.apache.org/jira/browse/HBASE-21035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16576279#comment-16576279
]
Duo Zhang commented on HBASE-21035:
-----------------------------------
The goal for HBASE-20708 is to remove the unnecessary scheduling for SCPs, and
also remove the usage of RecoverMetaProcedure, if you want to them back then
HBASE-20708 is useless...
I still stand my point, this is not the normal case as it breaks our
assumptions, we can provide tools for operators to override these errors, the
operators will take their own risk, but we should not try to address them in
the normal code path.
And if you think the procedure wal is not stable which may lead to corruption
files, please start to make it stable. And also we may introduce something like
a backup for the procedure wals to prevent manually damages.
> Meta Table should be able to online even if all procedures are lost
> -------------------------------------------------------------------
>
> Key: HBASE-21035
> URL: https://issues.apache.org/jira/browse/HBASE-21035
> Project: HBase
> Issue Type: Sub-task
> Affects Versions: 2.1.0
> Reporter: Allan Yang
> Assignee: Allan Yang
> Priority: Major
> Attachments: HBASE-21035.branch-2.0.001.patch
>
>
> After HBASE-20708, we changed the way we init after master starts. It will
> only check WAL dirs and compare to Zookeeper RS nodes to decide which server
> need to expire. For servers which's dir is ending with 'SPLITTING', we assure
> that there will be a SCP for it.
> But, if the server with the meta region crashed before master restarts, and
> if all the procedure wals are lost (due to bug, or deleted manually,
> whatever), the new restarted master will be stuck when initing. Since no one
> will bring meta region online.
> Although it is an anomaly case, but I think no matter what happens, we need
> to online meta region. Otherwise, we are sitting ducks, noting can be done.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
