[jira] [Updated] (HDFS-6133) Make Balancer support exclude specified path

["zhaoyunjiong (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HDFS-6133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

zhaoyunjiong updated HDFS-6133:
-------------------------------
    Attachment: HDFS-6133-4.patch

Thanks Yongjun Zhang.
Update patch according to comments.

{quote}
The concept of favoredNodes pre-existed before your patch, now your patch defines that as long as favoredNodes is passed, then pinning will be done. So we are changing the prior definition of how favoredNodes are used. Why not add some additional interface to tell that pinning will happen so we have the option not to pin even if favoredNodes is passed? Not necessarily you need to do what I suggested here, but I'd like to understand your thoughts here.
{quote}
I think most of time if you use favoredNodes, you'd like to keep the block on that machine, so to keep things simple, I didn't add new interface.
{quote}
Do we ever need interface to do unpinning?
{quote}
We can add unpinning in another issue if there are user case need that.

> 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.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)