hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron T. Myers (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4420) Provide a way to exclude subtree from balancing process
Date Fri, 18 Jan 2013 18:22:15 GMT

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

Aaron T. Myers commented on HDFS-4420:

Agree this would be a handy feature to have. The HBase example is a good one.

Max - to facilitate review/commit, please prepare a patch against trunk. Once that's reviewed/committed
to trunk and branch-2 we can do a back-port to branch-1.
> Provide a way to exclude subtree from balancing process
> -------------------------------------------------------
>                 Key: HDFS-4420
>                 URL: https://issues.apache.org/jira/browse/HDFS-4420
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: balancer
>    Affects Versions: 0.20.2
>            Reporter: Max Lapan
>            Priority: Minor
>             Fix For: 0.20.2
>         Attachments: Balancer-exclude-subtree-0.90.2.patch
> During balancer operation, it balances all blocks, regardless of their filesystem hierarchy.
Sometimes, it would be usefull to exclude some subtree from balancing process.
> For example, regionservers data locality is cruical for HBase performance. Region's data
is tied to regionservers, which reside on specific machines in cluster. During operation,
regionservers reads and writes region's data, and after some time, all this data are reside
on local machine, so, all reads become local, which is great for performance. Balancer breaks
this locality during opertation by moving blocks around.
> This patch adds [-exclude <path>] switch, and, if path is provided,
> balancer will not move blocks under this path during operation.
> Attached patch have tested for 0.90.2.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message