[
https://issues.apache.org/jira/browse/HBASE-5061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13176322#comment-13176322
]
Andrew Purtell commented on HBASE-5061:
---------------------------------------
bq. From looking at the code, this would produce data locality with respect to
certain host (if I understand this correctly).
Yes this is the intent, to report locality to a given regionserver host, by
default the local host as determined by a HBase style reverse lookup, assuming
ops would run it either on an ops box (or the master) and supply the desired
"local" host name via the '-h' option, or local to the RS.
I was thinking one use case could be to iterate over each cluster node and
trigger major compactions for region(s) depending on the output of this tool.
Of you are looking for a whole cluster report?
> StoreFileLocalityChecker
> ------------------------
>
> Key: HBASE-5061
> URL: https://issues.apache.org/jira/browse/HBASE-5061
> Project: HBase
> Issue Type: New Feature
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Priority: Minor
> Attachments: StoreFileLocalityChecker.java
>
>
> org.apache.hadoop.hbase.HFileLocalityChecker [options]
> A tool to report the number of local and nonlocal HFile blocks, and the ratio
> of as a percentage.
> Where options are:
> |-f <file>|Analyze a store file|
> |-r <region>|Analyze all store files for the region|
> |-t <table>|Analyze all store files for regions of the table served by the
> local regionserver|
> |-h <host>|Consider <host> local, defaults to the local host|
> |-v|Verbose operation|
--
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
