You install Cloudera Manager on a cluster where each host has 1 GB of RAM. All of the services
show their status as concerning. However, all jobs submitted complete without an error.
Why is Cloudera Manager showing the concerning status KM the services?

A.
A slave node’s disk ran out of space

B.
The slave nodes, haven’t sent a heartbeat in 60 minutes

C.
The slave nodes are swapping.

D.
DataNode service instance has crashed.

Explanation:
Concerning: There is an irregularity in the status of a service instance or role
instance, but Cloudera Manager calculates that the instance might recover. For example, if the
number of missed heartbeats exceeds a configurable threshold, the health status becomes
Concerning. Or, if an instance is running on a host and the host is rebooted, the instance will be
reported as In Progress for some period of time while it is restarting. Because the instance is
expected to be Started, its health will be reported as Concerning until it transitions to started.
Note:

Bad: The service instance or role instance is not performing or did not finish performing the last
command as expected, and Cloudera Manager calculates that the instance will not recover. For
example, if the number of missed heartbeats exceeds a second (higher) configurable threshold,
the health status becomes Bad. Another example of bad health is if a role you have stopped is
actually still running, or a started role has stopped unexpectedly.
Good: The service instance or role instance is performing or has finished performing the last
command as expected. This does not necessarily mean the service is running, it means it is
behaving as expected. For example, if you clicked Stop to stop a role instance and it stopped
successfully, then that role instance has a Good health status, even though it is not running.
About Service, Role, and Host Health