There is an API endpoint for starting all roles on a  host: https://archive.cloudera.com/cm7/7.2.4/generic/jar/cm_api/apidocs/resource_ClouderaManagerResource.html#resource_ClouderaManagerResource_ClouderaManagerResourceV41_hostsStartRolesCommand_POST   For stopping all roles on a host, you have to iterate in your script/code over all role instances deployed on the host, and stop them one after the other. ... View more

Hi Matt,   assuming you want to enable external authentication to LDAP in Cloudera Manager. Please find steps in the product documentation here for 6.x and here for 7.x  The steps you listed seem about right and should work. I suggest to verify if CM makes use of this JDK in the CM -> Support -> About page, and if necessary follow the steps in documentation to explicitly set the -Djavax.net.ssl.trustStore  and  -Djavax.net.ssl.trustStorePassword  startup properties. ... View more

CM does not start up because it can't connect to the backend database. Did you do a trial installation using  cloudera-manager-installer.bin ? Or did you you install using custom installed Postgresql database?   Please check if the database is up and running, and you can connect to it from CM host.   ... View more

That looks good, can you successfully connect when running this command on the CM host: # mysql -h tdicsadn01.td.com -u rman -p rman2019   ... View more

Likely user permissions on MySQL level. If you test mysql command connecting to hostname instead of localhost you likely see the same login recected: # mysql -h tdicsadn01.td.com -u rman -p rman2019  If so then please add grants for those two users for '%' or 'tdicsadn01.td.com' in MySQL as shown in Step 2 in corresponding documentation chapter ... View more

In CM you can also go to CM -> HDFS -> Click on active "Namenode" link -> Open "Actions" dropdown -> Select "Refresh node list" ... View more

My browser did not show your original question, which confirms the ask is about non-CM managed cluster upgrade. Please note this option has been removed, C6 requires Cloudera Manager installation. ... View more

Hi Alexander,   the upgrade consists of two steps Upgrading Cloudera Manager Upgrading CDH The steps to manually upgrade CDH are listed in Upgrading CDH Manually after an Upgrade Failure   Just in case the ask is about how to upgrade a non-CM managed cluster to 6.x, be aware that this option is not available anymore in C6, see Removed Items ... View more

What specific questions do you have regarding maintenance? Please clarify. ... View more

The same documentation chapters do apply, with the addition of How to Use Self-Signed Certificates for TLS chapter which has instructions for creating self-signed certificates.   As there is no CA certificate when using self-signed certificates, please add the server certificate of the service you are connecting to (e.g. CM server certificate) into the corresponding truststore file (like rootca.pem) ... View more

As this is only CM installation completed but no CDH cluster created already, it may be simpler to just start with an empty database for CM (and CMS services where needed) instead of migrating the current database. See instructions provided in the product documentation ... View more

Thanks for reporting back the root cause you've found! ... View more

Please set "-Xmx4G" in  /etc/default/cloudera-scm-server and restart CM, then test again. The apparent deadlock messages are an indicator of low memory condition and misleading, we need to make sure to cover the most likely root causes first.   ... View more

Please review the CM API docs  for CM 5.x http://cloudera.github.io/cm_api/apidocs/v19/index.html for CM 6.x https://archive.cloudera.com/cm6/6.2.0/generic/jar/cm_api/apidocs/index.html Posting a role object will make CM create that role e.g. http://cloudera.github.io/cm_api/apidocs/v19/path__clusters_-clusterName-_services_-serviceName-_roles.html   You may want to look into this end-to-end example in python as well. ... View more

Please review the sections in the Monitoring and Diagnostics documentation chapter. ... View more

CM commands (e.g. restart a role on a cluster node) time out after 150 seconds if there is no response sent back during this time. This happens e.g. if the CM agent on the cluster node is not heartbeating into CM server. Please increase heap memory for CM server in /etc/default/cloudera-scm-server (to avoid the apparent deadlock issue which indicates out of memory condition) make sure that all hosts are in good health state and heartbeating in in CM -> Hosts -> All Hosts page (the "Last Heartbeat" value needs to be lower than 15 seconds) If the host is not heartbeating in then the restart command will fail. The CM agent logs will hopefully show details, a quick resolution may be to restart the CM agent on that node with command  # service cloudera-scm-agent restart ... View more

Hi Nick,   you may want to have a look into the code at https://github.com/gdgt/cmapi This also covers sqoop installation and configuration ... View more