Thanks for the help.
So wierd thing my new host is present but however does not belong to the
cluster, you were right.
When I try to add it to the cluster it goes through the whole installation
process fine but times out at the end on waiting for cloudera agent signal
I have made sur the port 7182,9000,9001 are open and all in all, all ports
are open between my main machine and this new host.
My /etc/hosts file looks like:
127.0.0.1 localhost.localdomain localhost
On the new host in the cloudera agent log: I find
filesystem_map ERROR Timed out collecting nodev filesystem usage
which might be prt of the reason.
On Tue, Mar 5, 2013 at 6:03 PM, Mike Mellenthin wrote:
Is the host associated with a cluster? That is, what does the "Cluster"
column say for your new host on the Hosts page?
If it's not part of a cluster, or part of a different cluster, it won't
show up in the service you are trying to add it to.
On Tue, Mar 5, 2013 at 8:48 AM, Nicolas Maillard <email@example.com
I am using cloudera manager 4.5 and cdh 4.2
I have just added a new host to the cloudera manager through the web
The host is listed in the host tab and the host check says it's fine.
My problem is that I now what to use this host in the hdfs service as an
When I select the hdfs service and the add button in the instance tab I
see all my current hosts and their role but I don't see the new host.
I haa the same behaviour for all services, MR,hbase ...
My firewall is open on every port.
I fail to see what I am missign to add this new host to any service.
Thanks in advance for any input on this issue.