You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Allan Yang (JIRA)" <ji...@apache.org> on 2018/08/10 10:19:00 UTC

[jira] [Created] (HBASE-21035) Meta Table should be able to online even if all procedures are lost

Allan Yang created HBASE-21035:
----------------------------------

             Summary: 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


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 a 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)