[
https://issues.apache.org/jira/browse/HBASE-20546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471173#comment-16471173
]
Thiruvel Thirumoolan commented on HBASE-20546:
----------------------------------------------
Thanks [~chia7712]. Good point.
It looks like ClusterStatusChore will be updating clusterStatus. Its intention
is to make StochasticBalancer better by updating regionload. Not sure why
regionFinder's clusterstatus needs to be updated. I think we can have a
setClusterStatus and updateClusterStatus API, so ClusterStatusChore can use the
latter. I am not sure if updating clusterstatus or re-initializing the
hostserver map I introduce in regionfinder in the middle of balance is a good
idea. What do you think?
> Improve perf of RegionLocationFinder.mapHostNameToServerName
> ------------------------------------------------------------
>
> Key: HBASE-20546
> URL: https://issues.apache.org/jira/browse/HBASE-20546
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 1.4.4, 2.0.0
> Reporter: Thiruvel Thirumoolan
> Assignee: Thiruvel Thirumoolan
> Priority: Major
> Fix For: 1.5.0, 2.0.1, 1.4.5
>
> Attachments: HBASE-20546.branch-1.4.001.patch
>
>
> RegionLocationFinder.getTopBlockLocations() is called multiple times during
> balancer. While profiling on a large table balance, mapHostNameToServerName()
> seem to take a lot of time. One of the maps is repeatedly created for each
> iteration, while we can just initialize it once.
> Goes into both branch-1 and branch-2, although patches differ slightly.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
