[
https://issues.apache.org/jira/browse/HBASE-25211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17218365#comment-17218365
]
Viraj Jasani commented on HBASE-25211:
--------------------------------------
[~anoop.hbase] Indeed that is a good option, however, if we think about
building an automation around rack maintenance activities, the first thing we
would like the tool to perform is unload all regions from entire rack A to
other racks without having to worry about what are the current hosts available
on rack A.
Exclude and include hosts is nice option for an operator performing such
activities once in a while manually. Thought?
> Rack awareness in region_mover
> ------------------------------
>
> Key: HBASE-25211
> URL: https://issues.apache.org/jira/browse/HBASE-25211
> Project: HBase
> Issue Type: Improvement
> Reporter: Viraj Jasani
> Priority: Major
>
> region_mover should provide an option to ensure while unloading all regions,
> all destination servers are selected from different racks and not the one
> where server (where region_mover unload is getting executed) belongs to. This
> might be helpful option if we want to avail rack downtime (or rack upgrade)
> by stopping all Regionservers that belong to same rack for few hours. Without
> this option, we don't have any control over which destination server is
> selected and hence, some regions might keep bouncing from server A to B in
> the same rack all the way until they are finally moved to RS that belongs to
> separate rack.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
