Member since
04-28-2015
74
Posts
0
Kudos Received
7
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
3195 | 06-23-2021 12:17 AM | |
1284 | 02-18-2021 09:05 PM | |
2301 | 12-06-2019 08:31 PM | |
2987 | 10-17-2019 10:00 PM | |
4592 | 08-18-2019 11:29 PM |
06-23-2021
12:17 AM
Cluster restart also restarts Impala service. Could you please double check if following two properties are unchecked in CM > Impala > Configuration Enable Audit Collection Enable Impala Audit Event Generation To be able to disable auditing for Impala service, you need to uncheck both of the above options. Once done make sure to restart Impala service. CM would show stale and restart icon as well.
... View more
05-31-2021
10:16 PM
This is correct, if Enable Impala Audit Event Generation is unchecked, it will disable Impala daemon Audit logging, See documentation [1]. I hope after setting this property, you would have restarted Impala daemon roles. If not, restart now and after restart you should not see new audit files being created but old files would still be there. Can you check and confirm if these logs are generated on single Impala daemon hosts or on all Impala Daemon hosts even after it is disabled and Impala daemons restarted? [1] https://docs.cloudera.com/documentation/enterprise/6/6.3/topics/cn_admcfg_audit_log.html#configure_impala_daemon_log
... View more
02-18-2021
09:05 PM
Hi @pawski, Here is a solution for comparing CDH clusters configurations managed by different Cloudera Managers https://community.cloudera.com/t5/Support-Questions/Compare-settings-in-different-clusters/m-p/280536/highlight/true#M208909 Thanks, Salim
... View more
10-12-2020
05:37 AM
When you get below error message when doing kinit using a keytab file klist: Unsupported key table format version number while starting keytab scan Make sure that keytab file is not of zero byte e.g This is Zero byte keytab file and you will get the above error when trying to do kinit with it -rw------- 1 cloudera-scm cloudera-scm 0 Aug 30 12:15 ./32-cloudera-mgmt-SERVICEMONITOR/cmon.keytab A good keytab file will have non-zero size e.g. 778 for the below file -rw------- 1 cloudera-scm cloudera-scm 778 Oct 12 05:21 ./150-cloudera-mgmt-SERVICEMONITOR/cmon.keytab
... View more
01-28-2020
11:14 PM
Hi @lalprasanth , This error in screenshot indicates that while adding a new node in the cluster, the new node is not able to reach to CM server on port 7182 and the request timed out. Make sure that port 7182 is open. Test from new node if you are able to connect nc 182.156.238.158 7182 or telnet 182.156.238.158 7182 Thanks, Salim
... View more
12-06-2019
08:31 PM
Hi Devendra, I see you are seeing multiple low disk space alerts for various role log and role data directories. It is not advised to delete anything manually from these directories instead adjust the retention policy for them in CM and let CM delete it automatically for you. Review the documentation to find default retention policy for Cloudera Management Services data directories and following documentation for setting retention policy for any role log that by default reside in /var/log/. Remove and Delete any unused parcel from CM > Parcel page to reclaim disk space occupied by parcels. Details are given here. I hope that will help. Thanks, Salim
... View more
10-17-2019
10:00 PM
Hi All, Unfortunately, other than CM API there is no feature in CM itself to compare the cluster configuration with other cluster managed by another CM instance. In another case if you want compare the configuration settings for a particular service between two different clusters managed by same CM instance, you can do as per the steps given in the documentation here [1]. I suggest to go with CM CPI solution. You can use the CM API [2] to retrieve the full cluster configuration in JSON format including all hosts, clusters, services, roles, users, settings, etc. and use third party text compare tools like this [3] to compare them as text. It will highlight the difference in yellow. Another way is using diff command line. e.g. CM API example for getting full cluster configuration in browser in JSON format http://<your_cm_hostname>:7180/api/v12/cm/deployment Get the full cluster configuration using the API from both the CM servers and put them into the text comparator. I hope this will help. Regards, Salim [1] https://docs.cloudera.com/documentation/enterprise/5-13-x/topics/admin_compare_service_config_across_clusters.html#xd_583c10bfdbd326ba-7dae4aa6-147c30d0933--7c7c [2] https://cloudera.github.io/cm_api/apidocs/v12/path__cm_deployment.html [3] http://iblogbox.com/devtools/diff/
... View more
08-21-2019
12:05 PM
Hi @rssanders3, I hope you have seen the announcement but just to close the loop here CDSW 1.6 has been announced on July 24, 2019. Here is the public announcement with what's new and documentation link https://community.cloudera.com/t5/Product-Announcements/ANNOUNCE-Cloudera-Data-Science-Workbench-1-6-0-Released/td-p/93193 Yes, it will support RHEL/CentOS 7.6 along with 7.2, 7.3, 7.4, 7.5. Thanks, Salim
... View more
08-18-2019
11:29 PM
Hi, The error message confirms that the LevelDB holding the YARN state store is corrupt : org.apache.hadoop.service.ServiceStateException: org.fusesource.leveldbjni.internal.NativeDB$DBException: Corruption: 1 missing files; e.g.: /var/lib/hadoop-yarn/yarn-nm-recovery/yarn-nm-state/000042.sst Solution is to clean up and recreate the state store database : 1. In CM make sure the affected NodeManager has status STOP 2. Backup the contents under /var/lib/hadoop-yarn/yarn-nm-recovery/yarn-nm-state to a different directory. 3. Delete all the contents under /var/lib/hadoop-yarn/yarn-nm-recovery/yarn-nm-state. 4. Start affected NodeManager.
... View more
05-06-2018
12:02 AM
When a Cloudera Enterprise license expires, the following occurs: Cloudera Enterprise Enterprise Data Hub Edition Trial - Enterprise features are no longer available. Cloudera Enterprise - Cloudera Manager Admin Console displays a banner indicating license expiration. Contact Cloudera Support to receive an updated license. In the meanwhile, all enterprise features will continue to be available. This has been documented here.
... View more