[
https://issues.apache.org/jira/browse/HBASE-28168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780280#comment-17780280
]
Wellington Chevreuil commented on HBASE-28168:
----------------------------------------------
Thanks for the contribution [~mihir6692]. I had merged it to master, branch-3,
branch-2, branch-2.5 and branch-2.4.
> Add option in RegionMover.java to isolate one or more regions on the
> RegionSever
> --------------------------------------------------------------------------------
>
> Key: HBASE-28168
> URL: https://issues.apache.org/jira/browse/HBASE-28168
> Project: HBase
> Issue Type: New Feature
> Affects Versions: 2.6.0, 3.0.0-alpha-4, 2.4.17, 2.5.6, 4.0.0-alpha-1
> Reporter: Mihir Monani
> Assignee: Mihir Monani
> Priority: Minor
> Fix For: 2.6.0, 2.4.18, 3.0.0-beta-1, 4.0.0-alpha-1, 2.5.7
>
>
> 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.
> {code:java}
> --isolateRegionIds regionHash1,regionHash2,regionHash3{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
