Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Mon, 20 Apr 2015 17:12:59 +0000 (UTC)
From: "Dmitry Lysnichenko (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12822384.1429549934000.49232.1429549979251@Atlassian.JIRA>
In-Reply-To: <JIRA.12822384.1429549934000@Atlassian.JIRA>
References: <JIRA.12822384.1429549934000@Atlassian.JIRA>
 <JIRA.12822384.1429549934022@arcas>
Subject: [jira] [Created] (AMBARI-10608) Alerts: nodemanager health is
 critical, response is not clear
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Dmitry Lysnichenko created AMBARI-10608:
-------------------------------------------

             Summary: 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)