You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Anoop Sam John (Commented) (JIRA)" <ji...@apache.org> on 2012/02/23 14:17:49 UTC
[jira] [Commented] (HBASE-4491) HBase Locality Checker
[ https://issues.apache.org/jira/browse/HBASE-4491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13214617#comment-13214617 ]
Anoop Sam John commented on HBASE-4491:
---------------------------------------
@Liyin: Looks very useful. Any update on this new feature
> HBase Locality Checker
> ----------------------
>
> Key: HBASE-4491
> URL: https://issues.apache.org/jira/browse/HBASE-4491
> Project: HBase
> Issue Type: New Feature
> Reporter: Liyin Tang
> Assignee: 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira