You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2015/11/09 22:26:11 UTC

[jira] [Updated] (HBASE-14611) Backport HBASE-14473 (Compute region locality in parallel) to 0.98

     [ https://issues.apache.org/jira/browse/HBASE-14611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Purtell updated HBASE-14611:
-----------------------------------
      Resolution: Fixed
    Hadoop Flags: Reviewed
          Status: Resolved  (was: Patch Available)

Thanks for the reviews! Pushed to 0.98

> 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)