[
https://issues.apache.org/jira/browse/HBASE-24102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani updated HBASE-24102:
---------------------------------
Hadoop Flags: Reviewed
Resolution: Fixed
Status: Resolved (was: Patch Available)
Pushed to master and all branch-2s. It seems we can't backport this to branch-1
(No Admin API to get decommissioned servers list, no Admin API to decommission
servers either).
Thanks for the reviews [~reidchan] [~binlijin] [~pankajkumar] [~xucang]
[~stack] [~ram_krish]
> RegionMover should exclude draining/decommissioning nodes from target RSs
> -------------------------------------------------------------------------
>
> Key: HBASE-24102
> URL: https://issues.apache.org/jira/browse/HBASE-24102
> Project: HBase
> Issue Type: Improvement
> Reporter: Anoop Sam John
> Assignee: Viraj Jasani
> Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.4.0, 2.1.10, 2.2.5
>
>
> When using RegionMover tool to unload the regions from a given RS, it decides
> the list of destination RSs by
> {code}
> List<ServerName> regionServers = new ArrayList<>();
> regionServers.addAll(admin.getRegionServers());
> // Remove the host Region server from target Region Servers list
> ServerName server = stripServer(regionServers, hostname, port);
> .....
> // Remove RS present in the exclude file
> stripExcludes(regionServers);
> stripMaster(regionServers);
> {code}
> Ya it is removing the RSs mentioned in the exclude file.
> Better when the RegionMover user is NOT mentioning any exclude list, we can
> exclude the draining/decommissioning RSs
> Admin#listDecommissionedRegionServers()
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
