Support Questions
Find answers, ask questions, and share your expertise

[Cloudera manager 6.3 version] dfs.namenode.servicerpc-bind-host problem

[Cloudera manager 6.3 version] dfs.namenode.servicerpc-bind-host problem

New Contributor

Hello, I installed version 6.3 of  Cloudera Manager

 

In hdfs-site.conf , I modified it by adding dfs.namenode.servicerpc-bind-host as shown below.

 

cloudera.PNG

 

However, after restarting hdfs, the result is as shown below. I wanted to allow all IP connections using bind-host. Is it correct to change this setting?

 

cloudera2.PNG

1 REPLY 1

Re: [Cloudera manager 6.3 version] dfs.namenode.servicerpc-bind-host problem

Expert Contributor

Hi @songhwan 

 

By default HDFS endpoints are specified as either hostnames or IP addresses. In either case HDFS daemons will bind to a single IP address making the daemons unreachable from other networks.

The solution is to have separate setting for server endpoints to force binding the wildcard IP address INADDR_ANY i.e. 0.0.0.0. Do NOT supply a port number with any of these settings.

 

Usually in most of cluster those settings are bind to 0.0.0.0 to make namenode listen to all interfaces.

 

In case - If you have any issues with Namenode communication [wrt load or communication issue between namenode-datanode or block report] then you need to go for tuning this properties. Please check the link for details -

https://community.cloudera.com/t5/Community-Articles/Scaling-the-HDFS-NameNode-part-2/ta-p/246681

https://community.cloudera.com/t5/Community-Articles/Scaling-the-HDFS-NameNode-part-3-RPC-scalabilit...