[
https://issues.apache.org/jira/browse/HBASE-23035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17176848#comment-17176848
]
Anoop Sam John commented on HBASE-23035:
----------------------------------------
[~Bo Cui] So ur usecase is entire cluster restart and as part of that u want
the regions to come back to the old RSs itself (as much as possible). So
locality can be preserved.
There is a some config around the LB which takes whether to consider the data
locality aspect in deciding the plan. Can we make use of the same thing .. May
be not.. I dont remember details on that conf. [~zghao]
> Retain region to the last RegionServer make the failover slower
> ---------------------------------------------------------------
>
> Key: HBASE-23035
> URL: https://issues.apache.org/jira/browse/HBASE-23035
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 3.0.0-alpha-1, 2.3.0, 2.2.1, 2.1.6
> Reporter: Guanghao Zhang
> Assignee: Guanghao Zhang
> Priority: Major
> Fix For: 3.0.0-alpha-1, 2.3.0, 2.1.7, 2.2.2
>
>
> Now if one RS crashed, the regions will try to use the old location for the
> region deploy. But one RS only have 3 threads to open region by default. If a
> RS have hundreds of regions, the failover is very slower. Assign to same RS
> may have good locality if the Datanode is deploied on same host. But slower
> failover make the availability worse. And the locality is not big deal when
> deploy HBase on cloud.
> This was introduced by HBASE-18946.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
