02-14-2016 05:49 AM
I was interested in this threat since I encountered similar issues in a simple cluster config.
I'm using CM5 on CentOS 7.2
The host inspector gave :
The point is that each hosts is using a public IP address on eth0 and a private IP address on eth1.
As you can guess, I want my cluster to use the internal IP only.
I tried several things (between each stage, I restarted cloudera-scm-agent to make sure the modification is taken into account)
1- I tried to make some modifications to my /etc/hosts to precise public FQDN for public IP ==> FAIL
2 - I tried to use /etc/cloudera-scm/agent/config.ini , listening_ip to listen ONLY on the private IP ==> FAIL
3 - I tried to use /etc/cloudera-scm/agent/config.ini , listening_hostname to listen ONLY on the hostname associated with the private interface ==> FAIL.
At this stage, I can say, Cloudera agent is listening only on private interface (lsof confirmed) bue the inspector does not seem to focus on this
4 - I shut down eth0 (public interface) to disable multiple hostnames ==> SUCCESS
At this stage, I wondered why 3 fails and 4 succeeded. I think this is due to the python script below used to detect the hostname instead of using the cloudera config file :
python -c 'import socket; \
print socket.getfqdn(), \
This script seem to give the fqdn for eth0 first so no luck for me.
Not sure this is the solution but the trick worked for me. It could make sense if Cloudera staff review the inspector code and make sure python code know how to use the config file.
01-09-2018 11:00 AM
this fixed my problem with /etc/hosts
hope this helps someone else.
02-14-2018 12:37 AM
try add allow port on firewalld on host, this solved my prob
$ firewall-cmd --zone=public --add-port=9000/tcp
or $ service firewalld disable
Hope this may help