Member since
01-15-2015
313
Posts
28
Kudos Received
25
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 2044 | 10-19-2021 12:04 AM | |
| 6572 | 10-18-2021 11:54 PM | |
| 2357 | 05-04-2021 02:38 AM | |
| 9055 | 11-19-2020 05:48 AM | |
| 9087 | 11-18-2020 12:08 AM |
02-25-2019
06:41 AM
1 Kudo
Just a quick clarification, the DnsTest code calls straight the Java getHostName() and getCanonicalHostName() methods to retrieve the values. The reported mismatch was either caused by the name resolution settings at that time or by nscd caching the old values on the host.
... View more
02-25-2019
06:02 AM
1 Kudo
IMPALAD_QUERY_MONITORING_STATUS:
he health test result for IMPALAD_QUERY_MONITORING_STATUS has become bad: There are 1 error(s) seen monitoring executing queries, and 0 errors(s) seen monitoring completed queries for this role in the previous 5 minute(s). Critical threshold: any. Please see KB article Impala | IMPALAD_QUERY_MONITORING_STATUS has become bad for resolution.
... View more
02-25-2019
05:46 AM
1 Kudo
NAME_NODE_AUDIT_HEALTH:
The health test result for NAME_NODE_AUDIT_HEALTH has become bad: There is a problem processing audits for NAMENODE.
REGION_SERVER_AUDIT_HEALTH:
The health test result for REGION_SERVER_AUDIT_HEALTH has become bad: There is a problem processing audits for REGIONSERVER. Those indicate that there are issues sending the audit event logs created by these roles to the Navigator Audit Server. The root cause is either in the Navigator Audit Server or in the CM agent on the host with the role deployed to. Furher investigation needs to be to review the CM agent logs on the host(s) and the Navigator Audit Server logs at the time when the alert was raised. Any errors or exception seen at this time will indicate the root cause or at least provide pointers to base further investigation on.
... View more
02-25-2019
05:38 AM
1 Kudo
HIVESERVER2_SCM_HEALTH:
The health test result for HIVESERVER2_SCM_HEALTH has become bad: This role s process is starting. This role is supposed to be started. This should not be happening frequently, if it does please follow up with a support case. The issue can be resolved with instructions in KB article Role Managed by Cloudera Manager Stuck in Stopping or Starting State | Configured_Status
... View more
02-22-2019
01:55 AM
There won't be a generic fix for all these issues as they may have different root causes. Each type of alerts has to be looked into one by one, a root cause determined and corresponding action applied. This will be best done in a support case, if you have no contract then please post the exact health alert message for the most bugging alert you are getting here, and we will help to resolve the reported issues.
... View more
02-21-2019
06:51 AM
Thanks for confirming. Then the alert related settings appear to be correct. The way forward has to be to reduce the number of alerts raised for this cluster, either by resolving the related issues or by adjusting the corresponding alert thresholds if possible (or even disable the health test where unneeded). What kind of alerts do you see most frequently? Please share examples.
... View more
02-21-2019
06:21 AM
As a first step, please verify your settings following instructions in this KB article. In CM -> Administration -> Alerts, do you have these values set: Alert On Transitions Out of Alerting Health: No
Health Alert Threshold: Bad These are the default values, if e.g. the threshold is set to "Concerning" then please revert back to "Bad"
... View more
02-18-2019
01:41 AM
The SSL error means that the yum client could not agree with the server on TLS encryption properties. Is this a standard RHEL7 installation, or any customisation (e.g. hardening) applied? Is the system time correct? Are you behind a company proxy server? Please try "# yum clean all" command and try again. If you still see the error then please show content of /etc/yum.repos.d/cloudera.repo
... View more
02-18-2019
01:23 AM
1 Kudo
You will find this information in the CM -> Diagnostics -> Events page. Please review the corresponding documentation page
... View more
02-13-2019
12:30 AM
Please show the exact alert message, we need to know for which directory the free space warning is raised for. Likely this is for the /var mountpoint, in that case please confirm on actual disk usage with commands # df -h /var # du -hs /var/*
... View more
- « Previous
- Next »