[
https://issues.apache.org/jira/browse/HBASE-23035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16931181#comment-16931181
]
Anoop Sam John commented on HBASE-23035:
----------------------------------------
So the server which went down and immediate came back will have lesser regions
comparably right? In effect some of its old regions got moved to other live
RSs. So how/whether that will impact the cluster later? What will happen with
the later balance happening?
> 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: Bug
> Affects Versions: 3.0.0, 2.3.0, 2.2.1, 2.1.6
> Reporter: Guanghao Zhang
> Assignee: Guanghao Zhang
> Priority: Major
>
> 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.2#803003)
