You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2015/04/20 20:55:59 UTC
[jira] [Commented] (AMBARI-10608) Alerts: nodemanager health is
critical, response is not clear
[ https://issues.apache.org/jira/browse/AMBARI-10608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503417#comment-14503417 ]
Hudson commented on AMBARI-10608:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #2374 (See [https://builds.apache.org/job/Ambari-trunk-Commit/2374/])
AMBARI-10608. Alerts: nodemanager health is critical, response is not clear (dlysnichenko) (dlysnichenko: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=4e06a89f8625d0a03481028615a467470dfe54d9)
* ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/alerts/alert_nodemanager_health.py
> Alerts: nodemanager health is critical, response is not clear
> -------------------------------------------------------------
>
> Key: AMBARI-10608
> URL: https://issues.apache.org/jira/browse/AMBARI-10608
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Reporter: Dmitry Lysnichenko
> Assignee: Dmitry Lysnichenko
> Fix For: 2.1.0
>
> Attachments: AMBARI-10608.patch
>
>
> 5 node cluster, 5 NodeManager
> each has NodeManager Health alert instance
> All are critical
> response is: NodeManager returned an unexpected status of "False"
> Not sure what this means.
> If I check the ResourceManager, it does seem the NMs are unhealthy. But the alert response doesn't seem to give enough info to know what is going on
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)