Duo Zhang commented on HBASE-21035:

Anyway I'm -1 on doing anything automatically to try to recover if the core 
systems are broken. Here you are removing all the procedures so the solution 
maybe fine, as the error can not be recovered any more. But what if it is just 
a permission problem or something else? You bring meta online and mess up all 
the data and cause unrecoverable data loss...

For me, crash or hang is much much better than doing dangerous operations in 

> 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

Reply via email to