Member since
01-15-2015
313
Posts
28
Kudos Received
25
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
293 | 10-19-2021 12:04 AM | |
1110 | 10-18-2021 11:54 PM | |
639 | 05-04-2021 02:38 AM | |
2814 | 11-19-2020 05:48 AM | |
2846 | 11-18-2020 12:08 AM |
02-23-2022
11:14 PM
2 Kudos
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
12-14-2021
11:56 PM
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
10-19-2021
12:04 AM
There are several options for you here, you have to pick one that best matches your requirements. If you are looking to backup your HDFS data but don't have capacity for a DR cluster, then backup to AWS S3 may be an option for you. Requires a cluster upgrade to later 5.x version, though, as this option is not there on 5.4 version. Besides that, if you are able to completely restore the cluster nodes from your filesystem backups then you will be able to restore your HDFS data.
... View more
10-18-2021
11:54 PM
Starting/stopping cluster or services (and many other actions) will be done in Cloudera Manager UI or using the Cloudera Manager API The CM API can be used from curl commands in a shell script or when using the bindings from a Python script or Java code.
... View more
05-04-2021
02:38 AM
1 Kudo
Try something like # curl -u admin "http://$cmhost:7180/api/v33/clusters/Cluster%201/services/IMPALA-1/impalaQueries?filter=(query_state=RUNNING%20and%20query_duration>=1000)&from=2021-05-04T00:00:00.00Z"
... View more
11-23-2020
01:34 AM
1 Kudo
Great to hear @SuryaDilip ! Although I noticed my last update was not complete, I referenced the CM -> Administration -> Settings -> Category: Ports and Addresses -> Cloudera Manager Hostname Override configuration property.
... View more
11-19-2020
05:48 AM
1 Kudo
Thanks @SuryaDilip Lets try for a test to set CM -> Administration -> Settings -> Category: Ports and Addresses to the actual FQDN of the CM host. This needs a restart of CM server. After that change, update Alert Publisher config and re-enter the mail server hostname again, and restart Alert Publisher. Do you see the same exception in the Alert Publisher logs then, for a test alert?
... View more
11-18-2020
12:08 AM
1 Kudo
Thank you. That confirms alert email delivery fails because there is no SMTP daemon listening on localhost:25. I suspect there is a name resolution issue. Is the mail server hostname the host where CM is installed on, or a different host? Please login to CM, change the url in browser location bar to /cmf/debug/jmx and grep for MBeanServerId, does that show localhost or the correct hostname? What do those commands show: # getent hosts <mail server hostname> # getent hosts <cm server hostname> # getent hosts localhost
... View more
11-17-2020
01:12 AM
2 Kudos
Username/password is not strictly required for sending mails. This is not the cause for the issues you are seeing. Check the Alert Publisher logs for errors at the time when you hit the Send Test Alert button, there will be related errors shown why email delivery doesn't work yet.
... View more
08-10-2020
01:43 AM
2 Kudos
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
03-18-2020
12:26 AM
The clean and recommended way is to stop those services which are affected, before the backend database is shut down for maintenance (e.g. during maintenance window).
... View more
02-16-2020
11:32 PM
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
02-14-2020
02:45 AM
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
02-05-2020
12:34 AM
In CM you can also go to CM -> HDFS -> Click on active "Namenode" link -> Open "Actions" dropdown -> Select "Refresh node list"
... View more
01-14-2020
05:56 AM
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
01-14-2020
05:54 AM
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
01-13-2020
12:37 AM
What specific questions do you have regarding maintenance? Please clarify.
... View more
01-10-2020
12:39 AM
1 Kudo
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
10-23-2019
12:50 AM
Not exactly, this is not an issue at all but expected. It is what the error message says, the Spark 2.3 service is now (in C6) provided by the CDH parcel. There is no separate Spark2 parcel anymore, and you need to uninstall the Spark 2 parcel as advised in the doc chapter Migrating Apache Spark Before Upgrading to CDH 6
... View more
10-09-2019
12:25 AM
There are no plans to add support to C5 releases. See currently supported OS versions
... View more
07-31-2019
01:39 AM
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
06-25-2019
01:12 AM
Thanks for reporting back the root cause you've found!
... View more
06-19-2019
01:55 AM
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
06-17-2019
07:17 AM
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
06-17-2019
07:11 AM
Please review the sections in the Monitoring and Diagnostics documentation chapter.
... View more
06-17-2019
06:07 AM
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
05-25-2019
06:57 AM
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
05-15-2019
07:25 AM
Check bind-address in my.cnf config file, is it set to 127.0.0.1?
... View more
05-15-2019
01:24 AM
This confirmes the package is installed correctly, and the JDK is installed to /usr/lib/jvm/java-8-oracle-cloudera/ You may want to use this as JAVA_HOME when configuring CM and the cluster to use this JDK
... View more
05-14-2019
08:28 AM
Can you please verify your JDK installation: # apt list oracle-j2sdk1.8
# dpkg-query -L oracle-j2sdk1.8
... View more