hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean-Marc Spaggiari (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-6133) Make Balancer support exclude specified path
Date Fri, 25 Apr 2014 00:29:22 GMT

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

Jean-Marc Spaggiari commented on HDFS-6133:

I don't know if any other application outside of HBase need to avoid block movement, but the
pinning option you proposed might be fine for HBase. I will just recommend to have the option
to pin all the blocks and not just the first one. The thing is, HBase might a some point in
the future define "ghosts" regions on the replicates to improve performances or faster MTTR.
If we move those blocks that will again create same kind of concern.

So adding the ability to pin all the blocks or just one or none when creating them might be
a good option too for HBase.

> 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, namenode
>            Reporter: zhaoyunjiong
>            Assignee: zhaoyunjiong
>         Attachments: 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

View raw message