Reply
Explorer
Posts: 15
Registered: ‎03-14-2017
Accepted Solution

Datanode denied communication with namenode

Datanode unable to communicate with NameNode and getting following error message.  I am using cloudera 5.14.0 version and i do not have DNS

 

NN Static IP : 192.168.0.12 but it is trying other ip address 192.168.0.121

 

Did anyone face this issue earlier.. I am unable to proceed further.

 

Thanks in advance.

 

Error message.

18-06-13 19:02:29,352 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: Block pool BP-405258512-192.168.0.12-1528825240439 (Datanode Uuid 2bba9d98-a00c-40f0-9a0c-a479d071ba9f) service to cn3.hadoop.com/192.168.0.14:8022 beginning handshake with NN
2018-06-13 19:02:29,716 ERROR org.apache.hadoop.hdfs.server.datanode.DataNode: Initialization failed for Block pool BP-405258512-192.168.0.12-1528825240439 (Datanode Uuid 2bba9d98-a00c-40f0-9a0c-a479d071ba9f) service to cn3.hadoop.com/192.168.0.14:8022 Datanode denied communication with namenode because hostname cannot be resolved (ip=192.168.0.121, hostname=192.168.0.121): DatanodeRegistration(192.168.0.12, datanodeUuid=2bba9d98-a00c-40f0-9a0c-a479d071ba9f, infoPort=50075, infoSecurePort=0, ipcPort=50020, storageInfo=lv=-56;cid=cluster8;nsid=762896661;c=0)

Explorer
Posts: 15
Registered: ‎03-14-2017

Re: Datanode denied communication with namenode

I found following fix for Hadoop but  I am not sure how to fix cloudera

hdfs-site.xml - Need to add following line.

<property> <name>dfs.namenode.datanode.registration.ip-hostname-check</name> <value>false</value> </property>

Explorer
Posts: 15
Registered: ‎03-14-2017

Re: Datanode denied communication with namenode

It is a bug in 5.14.0 .. at last  I fixed it.

Announcements