hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rushabh S Shah (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HDFS-9083) Replication violates block placement policy.
Date Tue, 15 Sep 2015 19:12:46 GMT
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)
 if (!this.shouldCheckForEnoughRacks) {
      return true;
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

View raw message