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

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

    [ https://issues.apache.org/jira/browse/HBASE-21035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16576240#comment-16576240 ] 

Allan Yang edited comment on HBASE-21035 at 8/10/18 1:11 PM:
-------------------------------------------------------------

If scheduling a SCP for servers with '-splitting' is not a good idea, maybe we can go around. 
But before HBASE-20708, there is a method called processofflineServersWithOnlineRegions which will schedule a SCP for any dead server have regions on it(which will cause HBASE-20976...). But after HBASE-20708 there isn't( replaced by processOfflineRegions). Can we just bring the logic in processofflineServersWithOnlineRegions back? What I want is the same behave w/ or wo/ HBASE-20708.


was (Author: allan163):
If scheduling a SCP for servers with '-splitting' is not a good idea, then we can go around. Before HBASE-20708, there is a method called processofflineServersWithOnlineRegions which will schedule a assign procedure for any regions on a dead server. But after HBASE-20708 there isn't( replaced by processOfflineRegions). Can we just bring the logic in processofflineServersWithOnlineRegions back? What I want is the same behave w/ or wo/ HBASE-20708.

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