[
https://issues.apache.org/jira/browse/HBASE-17973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993831#comment-15993831
]
Josh Elser commented on HBASE-17973:
------------------------------------
bq. We usually name addendum patches as <original-patch-name>addendum<n>.patch
but clearly .003 is smaller than the others.
Thanks! I had only made a quick glance at a few other issues and didn't a
convention. Sorry, about that. I can re-attach+rename if you'd prefer.
Will push the addendum shortly.
> Create shell command to identify regions with poor locality
> -----------------------------------------------------------
>
> Key: HBASE-17973
> URL: https://issues.apache.org/jira/browse/HBASE-17973
> Project: HBase
> Issue Type: Improvement
> Components: shell
> Reporter: Josh Elser
> Assignee: Josh Elser
> Fix For: 2.0.0
>
> Attachments: HBASE-17973.001.patch, HBASE-17973.002.patch,
> HBASE-17973.003.patch
>
>
> The data locality of regions often plays a large role in the efficiency of
> HBase. Compactions are also expensive to execute, especially on very large
> tables. The balancer can do a good job trying to maintain locality (when
> tuned properly), but it is not perfect.
> This creates a less-than-desirable situation where it's a costly operation to
> take a cluster with spotty poor locality (e.g. a small percentage of
> regionservers with poor locality).
> We already have this information available via the {{ClusterStatus}} proto.
> We can easily write a shell command that can present regions which are
> lacking a certain percentage of locality.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
