05-10-2018 11:01 AM
By looking at the hostnames, I would guess that mgt01.cloudera is running the cloudera manager server.
Try logging into 10.0.2.100:7180 and see if the other 2 hosts are in that cluster.
Or you can try logging into each host and seeing if a cloudera agent or server is running. On redhat 7 those commands would be:
systemctl status cloudera-scm-server.service
systemctl status cloudera-scm-agent.service
Or see if there are any files under "ls /opt/cloudera"
Not sure what O/S you are running or if the install was cdh parcels or packages, but you can try looking around for cloudera files on those hosts.
05-19-2018 06:38 PM
this is a solved question !
aneways i m posting you the solution
if you click at the Cloudera supervisor logo, do you spot a cluster there?
if so, then i am guessing that the wizard created the cluster and assigned all hosts to it, but failed to yet configure the services.
the very best issue to do here is delete the cluster, then run the wizard once more by clicking upload Cluster.
The situation I defined could appear if the wizard failed barely in advance, after configuring CM agents however before developing the cluster.