[
https://issues.apache.org/jira/browse/HBASE-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-1066:
-------------------------
Attachment: 1066-v3.patch
Adds enable/disable and close region with optional removal of STARTCODE and
SERVER (so gets reassigned). Also added being able to specify servername you
want to send the close to in case META is not in agreement with whats out on
regionservers. Done as new commands in the shell: enable_region,
disable_region, and close_region. Need to add in help and figure why removal
of STARTCODE and SERVER does not always get a region reassigned.
> 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
> Fix For: 0.19.0
>
> Attachments: 1066-v3.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.
