Rushabh S Shah created HDFS-9083:
------------------------------------
Summary: Replication violates block placement policy.
Key: HDFS-9083
URL: https://issues.apache.org/jira/browse/HDFS-9083
Project: Hadoop HDFS
Issue Type: Bug
Components: HDFS, namenode
Affects Versions: 2.6.0
Reporter: Rushabh S Shah
Recently we are noticing many cases in which all the replica of the block are
residing on the same rack.
During the block creation, the block placement policy was honored.
But after node failure event in some specific manner, the block ends up in such
state.
On investigating more I found out that BlockManager#blockHasEnoughRacks is
dependent on the config (net.topology.script.file.name)
{noformat}
if (!this.shouldCheckForEnoughRacks) {
return true;
}
{noformat}
We specify DNSToSwitchMapping implementation (our own custom implementation)
via net.topology.node.switch.mapping.impl and no longer use
net.topology.script.file.name config.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
