You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Josh Elser (JIRA)" <ji...@apache.org> on 2017/05/01 21:56:04 UTC
[jira] [Reopened] (HBASE-17973) Create shell command to identify
regions with poor locality
[ https://issues.apache.org/jira/browse/HBASE-17973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Josh Elser reopened HBASE-17973:
--------------------------------
Apparently I'm terrible at writing Ruby tests for HBase.
Basic syntax error.. will resubmit with some more robust tests..
> 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
>
>
> 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)