[
https://issues.apache.org/jira/browse/HBASE-3833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13038067#comment-13038067
]
stack commented on HBASE-3833:
------------------------------
bq. In short, maybe we need a "force" option in decommissioning, which if used,
does not wait for a graceful shutdown of the specified regionserver, instead
declares it dead immediately and then follows the normal course of action
(lease recovery, reassign regions, etc)
Agreed. Seems like this patch does the 'forced' option. Missing from this
patch (though available as a script) is the graceful decommission. Vishal,
were you going for the 'forced' option only? If so, should we commit this
patch as is (though I think it dangerous if misunderstood and user is not clear
that excludes means 'forced' decommission).
> ability to support includes/excludes list in Hbase
> --------------------------------------------------
>
> Key: HBASE-3833
> URL: https://issues.apache.org/jira/browse/HBASE-3833
> Project: HBase
> Issue Type: Improvement
> Components: client, regionserver
> Affects Versions: 0.90.2
> Reporter: dhruba borthakur
> Assignee: dhruba borthakur
> Attachments: excl-patch.txt, excl-patch.txt
>
>
> An HBase cluster currently does not have the ability to specify that the
> master should accept regionservers only from a specified list. This helps
> preventing administrative errors where the same machine could be included in
> two clusters. It also allows the administrator to easily remove un-ssh-able
> machines from the cluster.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
