EM Incidents Generated by BDA Plugin Triggered by Cloudera Events are Not Being Cleared
(Doc ID 1924746.1)
Last updated on MARCH 03, 2020
Applies to:
Enterprise Manager for Big Data Appliance - Version 12.1.0.4.0 and laterLinux x86-64
Symptoms
NOTE: In the images, examples and document that follow, user details/information, environment data, cluster names, hostnames, directory paths, filenames, etc. represent a fictitious sample (and are used to provide an illustrative example only).
Oracle Big Data Appliance(BDA) is being monitored by 12.1.0.* BDA Enterprise Manager(EM) Plugin. When any of the CDH service/s managed by Cloudera Manager(CM) goes down, CM generates an event which is propagated as an incident to EM.
But the EM incident doesn't get Closed/Cleared even when the CDH service is up and in 'Good Health'.
Here is a sample CM triggered incident created in EM when Yarn service goes down.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |
References |