hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17973) Create shell command to identify regions with poor locality
Date Tue, 02 May 2017 00:20:04 GMT

    [ https://issues.apache.org/jira/browse/HBASE-17973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15991875#comment-15991875

Hudson commented on HBASE-17973:

SUCCESS: Integrated in Jenkins build HBase-Trunk_matrix #2933 (See [https://builds.apache.org/job/HBase-Trunk_matrix/2933/])
HBASE-17973 Expand list_regions to filter on data locality (elserj: rev 13b6fdf8ad81e236632a2dc99e6c4a317213858e)
* (edit) hbase-shell/src/main/ruby/shell/commands/list_regions.rb
* (add) hbase-shell/src/test/ruby/hbase/list_regions_test_no_cluster.rb
* (edit) hbase-shell/src/main/ruby/hbase_constants.rb

> 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

View raw message