[
https://issues.apache.org/jira/browse/HBASE-24208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17126733#comment-17126733
]
Viraj Jasani commented on HBASE-24208:
--------------------------------------
[~anoop.hbase] since 2.3 is under moratorium, how should we go about this?
Should this just go to master and branch-2 for now and we can open sub-task for
rest of 2.x commits after 2.3.0 is out?
> Remove RS entry from zk draining servers node after RS been stopped
> -------------------------------------------------------------------
>
> Key: HBASE-24208
> URL: https://issues.apache.org/jira/browse/HBASE-24208
> Project: HBase
> Issue Type: Improvement
> Reporter: Anoop Sam John
> Assignee: Gaurav Kanade
> Priority: Major
> Fix For: 3.0.0-alpha-1, 2.3.1, 2.2.6
>
>
> When a RS is been decommissioned, we will add an entry into the zk node. This
> will be there unless the same RS instance is recommissioned.
> But if we want to scale down a cluster, the best path would be to
> decommission the RSs in the scaling down nodes. The regions in these RSs
> will get moved to live RSs. In this case these decommissioned RSs will get
> stopped later. These will never get recommissioned. The zk nodes will still
> be there under draining servers path.
> We can remove this zk node when the RS is getting stopped.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
