hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colin Patrick McCabe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-6133) Make Balancer support exclude specified path
Date Thu, 19 Feb 2015 02:54:12 GMT

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

Colin Patrick McCabe commented on HDFS-6133:
--------------------------------------------

I apologize for coming into this discussion really late.  I am curious, though, why did we
decide to go with pinning rather than with the solution on HDFS-4420?  That solution seems
simpler because it doesn't require modifying the datanode.  Instead, we could just tell the
balancer to exclude the HBase paths.  Do you guys have some insight into this?

> 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, datanode
>            Reporter: zhaoyunjiong
>            Assignee: zhaoyunjiong
>             Fix For: 2.7.0
>
>         Attachments: HDFS-6133-1.patch, HDFS-6133-10.patch, HDFS-6133-11.patch, HDFS-6133-2.patch,
HDFS-6133-3.patch, HDFS-6133-4.patch, HDFS-6133-5.patch, HDFS-6133-6.patch, HDFS-6133-7.patch,
HDFS-6133-8.patch, HDFS-6133-9.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)

Mime
View raw message