[
https://issues.apache.org/jira/browse/HBASE-3833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13035859#comment-13035859
]
stack commented on HBASE-3833:
------------------------------
bq. 2. enqueues a shutdownhandler to move all the regions off this node
ServerShutdownHandler splits logs and reassigns regions that were (or *are* in
the decommissioning case) up on the shutdown server. It does not unload them
off the hosting regionserver. So, it looks to me as though regions can be in
two places at once... still on the server that has been marked decommissioned
and up in the new locations that ServerShutdownHandler has assigned them too.
This looks a little dangerous (if I am reading this right).
If decommissioning, it looks like you expire the server only at the end of the
server shutdown processing (your call to markServerExpiry will be noticed by
the hosting regionserver and it'll shut itself down closing out the regions it
was hosting).
New JIRA for Karthiks suggestion sounds good.
> 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
