The test connection page won't let you proceed unless your connection is valid.   Did you modify your service monitory database settings manually, after setting up the service?   What do the log messages say for the Service Monitor? Click on your Management Service, click on Service Monitory, click on the Processes tab, and look for any interesting messages in stderr, stdout, and the role log. ... View more

Hi Pankaj,   For your use-case, you want to use the host decommission command. This will move / re-replicate any data from that node to the rest of your cluster while stopping all roles, which will let you perform maintenance while the rest of the cluster is fully operational.   In the python bindings, the class ClouderaManager has the method hosts_decommission which will do exactly what you want.   Make sure to call the corresponding recommission command when you want it to re-join the cluster.   See the tutorial for general usage of the python bindings, including how to interact with commands: http://cloudera.github.io/cm_api/   Thanks, Darren ... View more

Hi Oleksiy,   Can you share the exact error message (ie copy and paste it here)? There's a few error messages that can sound similar, so it's good to verify which one we're talking about. If you click on the Hosts tab, then run the Hosts inspector, it will generate a report that will list the software versions on each host, along with errors such as version mismatches. Please share this page with us.   Thanks, Darren ... View more

Your restart command for agents is correct.   Did your agents change host names / ip addresses as well? It sounds like your hosts page has two entries for each host, one with the new name, one with the old. In this case, you need to tell your agents to use the old host id. You don't want to use the new host id because you'll have to re-configure all of your role assignments. Edit /etc/default/cloudera-scm-agent and set CMF_AGENT_ARGS="--host_id xxx" where xxx is your old host id. You can find the old host id by clicking on your old host in the Hosts tab and looking at what is listed for Host ID.   Restart your agents after changing /etc/default/cloudera-scm-agent.   On the Hosts page, you should see all of your old hosts (the ones with roles assigned to them) have recent heartbeats and good health. You can delete the copies that have no heartbeats and no roles. If you don't see this, then let us know what you see so we can fix it.   Now Cloudera Manager is correctly in contact with all of your hosts again. You can run the restart command through the Cloudera Manager UI. You can restart an individual service or the whole cluster by clicking on the appropriate dropdown menu (small button with a triangle).   Thanks, Darren ... View more