[
https://issues.apache.org/jira/browse/HBASE-14611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14998945#comment-14998945
]
Hudson commented on HBASE-14611:
--------------------------------
FAILURE: Integrated in HBase-0.98-on-Hadoop-1.1 #1131 (See
[https://builds.apache.org/job/HBase-0.98-on-Hadoop-1.1/1131/])
HBASE-14611 Backport HBASE-14473 (Compute region locality in parallel)
(apurtell: rev 70b9015a0ec8de5ed9f9d9302b67b8e79bc4c558)
*
hbase-server/src/main/java/org/apache/hadoop/hbase/master/balancer/RegionLocationFinder.java
> Backport HBASE-14473 (Compute region locality in parallel) to 0.98
> ------------------------------------------------------------------
>
> Key: HBASE-14611
> URL: https://issues.apache.org/jira/browse/HBASE-14611
> Project: HBase
> Issue Type: Task
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Fix For: 0.98.16
>
> Attachments: HBASE-14611-0.98.patch
>
>
> [~eclark] contributed a nice change on HBASE-14473 that scales calculation of
> locality balance cost to larger clusters. I'd like to bring this back to 0.98
> for folks running it on larger clusters. The changes require a partial
> rewrite of RegionLocationFinder hence a backport issue.
> The difference between this backport and RegionLocationFinder on later
> branches is we preserve the ability to change the expiration time of cache
> items with the configuration parameter
> "hbase.master.balancer.regionLocationCacheTime".
> The difference between RegionLocationFinder in 0.98 before and after this
> change is the expiration time of cache entries will be set according to when
> they are written into the cache instead of from when they are last accessed,
> which seems better to me.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
