[
https://issues.apache.org/jira/browse/HBASE-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12658167#action_12658167
]
stack commented on HBASE-1066:
------------------------------
Agreed.
You can do some of this now but its more awkward than it need be. To
enable/disable individual region, you'd write a script that got info:regioninfo
cell from .META., rendered it as HRI, set the particular flag, then wrote it
back. If master has a region and no HRS does, then setting the server to null
will force the master to reassign. Both of the above can be done in two or
three lines of script but error-prone and for the congnescenti. I agree we
need it fixing broke clusters and the facility should be more amenable to
admins.
> 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
>
> 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.
