[
https://issues.apache.org/jira/browse/HDFS-6133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14313417#comment-14313417
]
Tsz Wo Nicholas Sze commented on HDFS-6133:
-------------------------------------------
> You mean choosing the mechanism don't rely on the os but rely on the
> mechanism only?
Admins can choose which the mechanism they want to use. Of course, we should
throw an error if they choose sticky bit in Windows.
Sticky bit is more preferable but the support of sticky bit is not standard.
Some systems does not support it. Even for the systems supporting it, they may
have different meaning. So I think we need to allow admin to choose the
mechanism.
> 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-10.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)
