[
https://issues.apache.org/jira/browse/HBASE-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-1066.
--------------------------
Resolution: Fixed
Committed after removing notion of clean. It doesn't add anything. Can not
clean the SERVER and STARTCODE but hbase will assign the region again anyways
in the region close handler. Can add more tools easy enough as we go. This
should do as a start.
> 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.
