Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 1 Feb 2017 23:14:51 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.13039634.1485990883000.11869.1485990891691@Atlassian.JIRA>
In-Reply-To: <JIRA.13039634.1485990883000@Atlassian.JIRA>
References: <JIRA.13039634.1485990883000@Atlassian.JIRA> <JIRA.13039634.1485990883095@jira-lw-us.apache.org>
Subject: [jira] [Created] (HBASE-17580) Tooling to move table out of
 FAILED_OPEN state
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 01 Feb 2017 23:14:57 -0000

stack created HBASE-17580:
-----------------------------

             Summary: Tooling to move table out of FAILED_OPEN state
                 Key: HBASE-17580
                 URL: https://issues.apache.org/jira/browse/HBASE-17580
             Project: HBase
          Issue Type: Sub-task
          Components: Region Assignment
    Affects Versions: 2.0.0
            Reporter: stack
            Priority: Critical


Playing with rsgroup feature, I was able to manufacture a state where assignment landed regions into a FAILED_OPEN state; i.e. assignment could not complete (in this case because no server for the region to land on inside its rsgroup). Once in this FAILED_OPEN state, the only way currently (seemingly) to move it on from this state is to manually assign the region. If table is large, this is burdensome. FAILED_OPEN seems a legitmate endpoint for AM to dump regions into if it can't do anything with them. We need tooling for 'fix'. One thought is that assign take a tableName.

Disable/Enable does not work.


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)