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

Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2017/05/24 22:42:04 UTC

[jira] [Resolved] (HBASE-17580) Tooling to move table out of FAILED_OPEN state

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

stack resolved HBASE-17580.
---------------------------
    Resolution: Duplicate

Resolving as duplicate of HBASE-14620 This is a HSCK issue.

> 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
>             Fix For: 2.0.0
>
>
> 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)