Reply
New Contributor
Posts: 5
Registered: ‎10-12-2016

Namenode/Resource Manager Bad Health

Hi Team,

After a new install of CM and CDH5(5.8.1 & 5.8.0) , i am getting the following Namenode/Resource manager error eventhough Namenode/Resource manger service are up & running. 

I am not able see any errors reported on Service monitor logs.

 

Errors :

 

Bad : NameNode summary: hostname1(Availability: Unknown, Health: Good). This health test is bad because the Service Monitor did not find an active NameNode.
Bad : ResourceManager summary: hostname1(Availability: Unknown, Health: Good). This health test is bad because the Service Monitor did not find an active ResourceManager.

 

 

Thanks,

Kumar

 

Thanks,

Kumar

New Contributor
Posts: 2
Registered: ‎05-24-2017

Re: Namenode/Resource Manager Bad Health

Hi, i have the same problem, have you found the cause?
Posts: 1,827
Kudos: 406
Solutions: 292
Registered: ‎07-31-2013

Re: Namenode/Resource Manager Bad Health

Look for messages in the CM agent log local to the NameNode/ResourceManager host that mention the host:port (50070/8088/etc.) of the NN/RM.

The agent is responsible for collecting metrics and states and sends these to the Service Monitor. Its likely the agent has ceased sending any information, and that's why your Service Monitor is showing unknown states for certain health checks.
Announcements