You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2014/12/24 21:13:14 UTC

[jira] [Resolved] (HBASE-4491) HBase Locality Checker

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

Andrew Purtell resolved HBASE-4491.
-----------------------------------
    Resolution: Duplicate
      Assignee:     (was: Liyin Tang)

> HBase Locality Checker
> ----------------------
>
>                 Key: HBASE-4491
>                 URL: https://issues.apache.org/jira/browse/HBASE-4491
>             Project: HBase
>          Issue Type: New Feature
>            Reporter: Liyin Tang
>
> If we run data node and region server in the same physical machine, region server will be benefit if the store files for its serving regions have a local replica in the data node process.
> So for each regions, there exists a best locality region server which has most local blocks for this region.
> The HBase Locality Checker will show how many regions is running on its best locality region server. 
> The higher the number is, the more performance benefits HBase can get from data locality.
> Also there would be a followup task to use these region locality information for region assignment. Assignment manager will prefer assign regions to its best locality region server.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)