[ https://issues.apache.org/jira/browse/HDFS-4521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13606320#comment-13606320 ]
Hudson commented on HDFS-4521: ------------------------------ Integrated in Hadoop-Mapreduce-trunk #1377 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1377/]) HDFS-4521. Invalid network toploogies should not be cached. Contributed by Colin Patrick McCabe. (Revision 1457878) Result = FAILURE atm : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1457878 Files : * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/net/CachedDNSToSwitchMapping.java * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/net/DNSToSwitchMapping.java * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/net/NetworkTopology.java * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/net/NodeBase.java * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/net/ScriptBasedMapping.java * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/net/TableMapping.java * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/net/StaticMapping.java * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/net/TestSwitchMapping.java * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/net/TestTableMapping.java * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/blockmanagement/DatanodeManager.java * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/net/TestNetworkTopology.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-hs/src/test/java/org/apache/hadoop/mapreduce/v2/hs/TestJobHistoryParsing.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/test/java/org/apache/hadoop/yarn/util/TestRackResolver.java > invalid network toploogies should not be cached > ----------------------------------------------- > > Key: HDFS-4521 > URL: https://issues.apache.org/jira/browse/HDFS-4521 > Project: Hadoop HDFS > Issue Type: Improvement > Affects Versions: 2.0.5-beta > Reporter: Colin Patrick McCabe > Assignee: Colin Patrick McCabe > Priority: Minor > Fix For: 2.0.5-beta > > Attachments: HDFS-4521.001.patch, HDFS-4521.002.patch, > HDFS-4521.005.patch, HDFS-4521.006.patch, HDFS-4521.008.patch > > > When the network topology is invalid, the DataNode refuses to start with a > message such as this: > {quote} > org.apache.hadoop.hdfs.server.protocol.DatanodeProtocol.registerDatanode from > 172.29.122.23:55886: error: > org.apache.hadoop.net.NetworkTopology$InvalidTopologyException: Invalid > network topology. You cannot have a rack and a non-rack node at the same > level of the network topology. > {quote} > This is expected if you specify a topology file or script which puts leaf > nodes at two different depths. However, one problem we have now is that this > incorrect topology is cached forever. Once the NameNode sees it, this > DataNode can never be added to the cluster, since this exception will be > rethrown each time. The NameNode will not check to see if the topology file > or script has changed. We should clear the topology mappings when there is > an InvalidTopologyException, to prevent this problem. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira