[HBASE-28168] Add option in RegionMover.java to isolate one or more regions on the RegionSever

• Type: New Feature
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.6.0, 3.0.0-alpha-4, 2.4.17, 2.5.6, 4.0.0-alpha-1
• Fix Version/s: 2.6.0, 2.4.18, 3.0.0-beta-1, 2.5.7

Release Note

This adds a new "isolate_regions" operation to RegionMover, which allows operators to pass a list of region encoded ids to be "isolated" in the passed RegionServer.
Regions currently deployed in the RegionServer that are not in the passed list of regions would be moved to other RegionServers. Regions in the passed list that are currently on other RegionServers would be moved to the passed RegionServer.

Please refer to the command help for further information.

• Assignee: Mihir Monani
• Reporter: Mihir Monani
• Created: 19/Oct/23 04:20
• Updated: 26/Dec/23 10:05
• Resolved: 27/Oct/23 09:39

Description

Sometime one or more HBase regions on RS are under high load. This can lead to resource starvation for other regions hosted on the RS. It might be necessary to isolate one or more regions on the RS so that region with heavy load doesn't impact other regions hosted on the same RS.

RegionMover.java class provides a way to load/unload the regions from the specific RS. It would be a good to have an option to pass list of region hash that should be left (or moved) on the RS and put the RS in the draining/decommission mode so HMaster doesn't assign new regions on the RS.

Ex.

--isolateRegionIds regionHash1,regionHash2,regionHash3

Issue Links

• links to: GitHub Pull Request #5470
• links to: GitHub Pull Request #5476