Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Date: Sat, 10 Jan 2015 01:52:35 +0000 (UTC)
From: "Andrew Purtell (JIRA)" <jira@apache.org>
To: dev@hbase.apache.org
Message-ID: <JIRA.12546204.1331630134000.52896.1420854755102@Atlassian.JIRA>
In-Reply-To: <JIRA.12546204.1331630134000@Atlassian.JIRA>
References: <JIRA.12546204.1331630134000@Atlassian.JIRA>
 <JIRA.12546204.1331630134721@arcas>
Subject: [jira] [Resolved] (HBASE-5571) Table will be disabling forever
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Andrew Purtell resolved HBASE-5571.
-----------------------------------
    Resolution: Won't Fix
      Assignee:     (was: chunhui shen)

Thanks for looking at this [~clehene]. Reported against now unsupported version 0.90, resolving as Wont Fix

> Table will be disabling forever
> -------------------------------
>
>                 Key: HBASE-5571
>                 URL: https://issues.apache.org/jira/browse/HBASE-5571
>             Project: HBase
>          Issue Type: Bug
>          Components: master, regionserver
>            Reporter: chunhui shen
>         Attachments: BASE-5571v2.patch, HBASE-5571.patch, HBASE-5571v3.patch
>
>
> If we restart master when it is disabling one table, the table will be disabling forever.
> In current logic, Region CLOSE RPC will always returned NotServingRegionException because RS has already closed the region before we restart master. So table will be disabling forever because the region will in RIT all along.
> In another case, when AssignmentManager#rebuildUserRegions(), it will put parent regions to AssignmentManager.regions, so we can't close these parent regions until it is purged by CatalogJanitor if we execute disabling the table.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)