hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From surendra lilhore <surendra.lilh...@huawei.com>
Subject Issue with DN and NN connection.
Date Mon, 22 Sep 2014 07:02:10 GMT
Hi all,

                I just found one issue in DataNode and Namenode connection. I am not sure
it is issue or not.

                Issue :

                                My one DN machine have two IP (float and private).
                                I have configured private IP in "dfs.datanode.address" .

                                But when my DN stated, it's using float IP for namenode communication.

                                Here is private and is float IP for
DN machine

                                  netstat -tanpl | grep 2394

In my namenode machine( for DN float IP /etc/hosts mapping is not there , so Datanode
registration is failing saying "not able to get DN hostname".

                                Logs from Namenode
org.apache.hadoop.hdfs.server.protocol.DisallowedDatanodeException: Datanode denied communication
with namenode because hostname cannot be resolved (ip=, hostname=
DatanodeRegistration(, datanodeUuid=0ed5012a-7ef6-4b55-b87b-fec70296faa3, infoPort=25002,
ipcPort=50020, storageInfo=lv=-55;cid=myhacluster;nsid=1613974306;c=0)
       at org.apache.hadoop.hdfs.server.blockmanagement.DatanodeManager.registerDatanode(DatanodeManager.java:806)
       at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.registerDatanode(FSNamesystem.java:4313)

                                My question is "why DN is using float IP for Namenode communication
?", it should use private IP only because in  "dfs.datanode.address" I have configured private

Thanks & Regards

This e-mail and its attachments contain confidential information from HUAWEI, which is intended
only for the person or entity whose address is listed above. Any use of the information contained
herein in any way (including, but not limited to, total or partial disclosure, reproduction,
or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive
this e-mail in error, please notify the sender by phone or email immediately and delete it!

  • Unnamed multipart/related (inline, None, 0 bytes)
View raw message