hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Duo Zhang (Jira)" <j...@apache.org>
Subject [jira] [Resolved] (HBASE-21035) Meta Table should be able to online even if all procedures are lost
Date Thu, 21 Nov 2019 14:01:00 GMT

     [ https://issues.apache.org/jira/browse/HBASE-21035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Duo Zhang resolved HBASE-21035.
-------------------------------
    Resolution: Won't Fix

I think now we can use HBCK2 to deal with this.

> 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, HBASE-21035.branch-2.1.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
(v8.3.4#803005)

Mime
View raw message