You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "zhaoyunjiong (JIRA)" <ji...@apache.org> on 2014/12/22 08:50:14 UTC
[jira] [Updated] (HDFS-6133) Make Balancer support exclude
specified path
[ https://issues.apache.org/jira/browse/HDFS-6133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
zhaoyunjiong updated HDFS-6133:
-------------------------------
Attachment: HDFS-6133-6.patch
Thanks Kai Zheng for point out the bug in TestBalancer. Fixed in new patch.
Also update the comment mentioned.
For mover, it use replaceBlock same as balancer, so mover will not able to move blocks as well.
For torage type/policy, Kihwal Lee already answered the question:
{quote}
We will make additional changes in separate jiras to make NN aware of favored nodes. I think the patch in this jira is fine as a stepping stone for the further work.
{quote}
> Make Balancer support exclude specified path
> --------------------------------------------
>
> Key: HDFS-6133
> URL: https://issues.apache.org/jira/browse/HDFS-6133
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: balancer & mover, namenode
> Reporter: zhaoyunjiong
> Assignee: zhaoyunjiong
> Attachments: HDFS-6133-1.patch, HDFS-6133-2.patch, HDFS-6133-3.patch, HDFS-6133-4.patch, HDFS-6133-5.patch, HDFS-6133-6.patch, HDFS-6133.patch
>
>
> Currently, run Balancer will destroying Regionserver's data locality.
> If getBlocks could exclude blocks belongs to files which have specific path prefix, like "/hbase", then we can run Balancer without destroying Regionserver's data locality.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)