You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Gavin (JIRA)" <ji...@apache.org> on 2018/08/01 06:22:20 UTC

[jira] [Issue Comment Deleted] (HBASE-20514) On Master restart if table is stuck in DISABLING state, CLOSED regions should not be considered stuck in-transition

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

Gavin updated HBASE-20514:
--------------------------
    Comment: was deleted

(was: A comment with security level 'jira-users' was removed.)

> On Master restart if table is stuck in DISABLING state, CLOSED regions should not be considered stuck in-transition
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-20514
>                 URL: https://issues.apache.org/jira/browse/HBASE-20514
>             Project: HBase
>          Issue Type: Bug
>          Components: amv2
>    Affects Versions: 2.0.0
>            Reporter: Umesh Agashe
>            Assignee: Umesh Agashe
>            Priority: Major
>             Fix For: 2.0.1
>
>         Attachments: hbase-20514.master.001.patch
>
>
> When master is restarted, in AssignmentManager#loadMeta(), if table is in DISABLED state nothing is done for regions in CLOSED state. But if table is stuck in DISABLING state then CLOSED regions are considered as stuck in-transition. CLOSED regions of DISABLING/ DISABLED table can be handled the same way.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)