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 2008/12/23 23:32:44 UTC

[jira] Assigned: (HBASE-1066) Master should support close/open/reassignment/enable/disable operations on individual regions

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

stack reassigned HBASE-1066:
----------------------------

    Assignee: stack

> Master should support close/open/reassignment/enable/disable operations on individual regions
> ---------------------------------------------------------------------------------------------
>
>                 Key: HBASE-1066
>                 URL: https://issues.apache.org/jira/browse/HBASE-1066
>             Project: Hadoop HBase
>          Issue Type: Improvement
>            Reporter: Andrew Purtell
>            Assignee: stack
>             Fix For: 0.19.0
>
>         Attachments: 1066-v3.patch, 1066-v4.patch, 1066.patch
>
>
> The master should support close/open/reassignment/enable/disable operations on individual regions by way of a client API and corresponding shell command(s), and maybe also controls on the master UI.
>  
> If one region out of 1000s is closed or offline, for example due to transient DFS problems, currently the whole table must be disabled, then reenabled to trigger reassignment and, hopefully, successful (re)open of the offline regions. The flurry of compactions this causes can exacerbate the underlying problem and actually make cluster state worse, as more DFS errors accumulate. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.