Member since
01-15-2015
313
Posts
28
Kudos Received
25
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
1182 | 10-19-2021 12:04 AM | |
4692 | 10-18-2021 11:54 PM | |
1708 | 05-04-2021 02:38 AM | |
6551 | 11-19-2020 05:48 AM | |
6583 | 11-18-2020 12:08 AM |
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
02-12-2019
12:54 AM
To answer your questions: The Time Series Storage limit can be configured but the minimum value is 10 Gb. Data is deleted from time series when this limit is reached. A change for this configuration parameter requires a restart of the role instance. Please note that this is all about time series data which will be used to populate the charts in Cloudera Manager with data. This will not affect the log file size for the roles, e.g. in /var/log/cloudera-scm-firehose/ directory, as you mention /logs again in your recent post.
... View more
02-11-2019
06:49 AM
In my understanding the question was not about timeseries storage but actual role log files, is this correct @wert_1311 ? Please note that there are only log file size oriented options available for Cloudera Management Services and cluster services, but no time based options.
... View more
02-07-2019
06:02 AM
1 Kudo
Please configure more heap memory for the Cloudera Mangager process, follow instructions as shown in Increasing Max Heap Size | Cloudera Manager Service Control Manager Please note those messages which state "no GCs detected" indicate the host is overloaded cpu wise.
... View more
01-16-2019
03:18 AM
In addition to that, can you please show us the CM agent configuration with # egrep -v '^[[:blank:]]*#|^$' /etc/cloudera-scm-agent/config.ini
... View more