[
https://issues.apache.org/jira/browse/HADOOP-8928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13503347#comment-13503347
]
liang xie commented on HADOOP-8928:
-----------------------------------
Before applied the patch, if we add a new datanode, it may encourter the
following exception:
org.apache.hadoop.ipc.RemoteException(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.
at org.apache.hadoop.net.NetworkTopology.add(NetworkTopology.java:365)
at
org.apache.hadoop.hdfs.server.blockmanagement.DatanodeManager.registerDatanode(DatanodeManager.java:619)
2012-11-23 17:47:31,790 INFO org.apache.hadoop.net.NetworkTopology: Removing a
node: /default-rack/10.235.2.214:50010
2012-11-23 17:47:31,790 INFO org.apache.hadoop.net.NetworkTopology: Adding a
new node: /default-rack/10.235.2.214:50010
2012-11-23 17:47:31,790 ERROR org.apache.hadoop.net.NetworkTopology: Error:
can't add leaf node at depth 2 to topology:
Number of racks: 3
Expected number of leaves:3
/sd/rack3/10.235.2.212:50010
/sd/rack2/10.235.2.211:50010
/gg/rack1/10.235.2.213:50010
2012-11-23 17:47:31,790 WARN org.apache.hadoop.ipc.Server: IPC Server handler
31 on 8020, call
org.apache.hadoop.hdfs.server.protocol.DatanodeProtocol.registerDatanode from
10.235.2.214:35059: 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.
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.
at org.apache.hadoop.net.NetworkTopology.add(NetworkTopology.java:365)
at
org.apache.hadoop.hdfs.server.blockmanagement.DatanodeManager.registerDatanode(DatanodeManager.java:619)
at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.registerDatanode(FSNamesystem.java:3358)
at
org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.registerDatanode(NameNodeRpcServer.java:860)
at
org.apache.hadoop.hdfs.protocolPB.DatanodeProtocolServerSideTranslatorPB.registerDatanode(DatanodeProtocolServerSideTranslatorPB.java:91)
> Add ability to reset topologies on master nodes
> -----------------------------------------------
>
> Key: HADOOP-8928
> URL: https://issues.apache.org/jira/browse/HADOOP-8928
> Project: Hadoop Common
> Issue Type: Improvement
> Components: net
> Affects Versions: 3.0.0, 2.0.2-alpha
> Reporter: Shinichi Yamashita
> Attachments: HADOOP-8928.txt
>
>
> For a topology decision of DataNode and TaskTracker, ScriptBasedMapping
> (probably TableMapping) confirms HashMap first.
> To decide topology of DataNode and TaskTracker again, it is necessary to
> restart NameNode and JobTracker.
> Therefore, it is necessary to change (or clear) HashMap function without
> restarting NameNode and JobTracker.
--
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
