[
https://issues.apache.org/jira/browse/HDFS-6133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13987736#comment-13987736
]
Daryn Sharp commented on HDFS-6133:
-----------------------------------
I'm not sure the NN needs to know about the pinning. It may only need to be
something the client tells the DN when establishing the pipeline. Perhaps it
could be stored in the existing block metadata file is, but I don't know how
extensible the file is, whether it can be changed with backwards compatibility,
etc. Other approaches might be using the sticky bit or the existence of a
second file to denote a pinned block.
> 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
(v6.2#6252)
