[
https://issues.apache.org/jira/browse/HDFS-6133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yongjun Zhang updated HDFS-6133:
--------------------------------
Release Note: Add a feature for replica pinning so that when a replica is
pinned in a datanode, it will not be moved by Balancer/Mover. The replica
pinning feature can be enabled/disabled by
"dfs.datanode.block-pinning.enabled". This feature is disabled by default,
(was: Add a feature for replica pinning so that when a replica is pinned in a
datanode, it will not be moved by Balancer/Mover. The replica pinning feature
can be enabled/disabled by client config property
"dfs.client.pin-on-favored-node.enabled" whose default is false.)
> Add a feature for replica pinning so that a pinned replica will not be moved
> by Balancer/Mover.
> -----------------------------------------------------------------------------------------------
>
> 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)
