Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Wed, 23 Nov 2016 16:11:58 +0000 (UTC)
From: "Tim Thorpe (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.13021675.1479446418000.352225.1479917518615@Atlassian.JIRA>
In-Reply-To: <JIRA.13021675.1479446418000@Atlassian.JIRA>
References: <JIRA.13021675.1479446418000@Atlassian.JIRA> <JIRA.13021675.1479446418861@arcas>
Subject: [jira] [Commented] (AMBARI-18929) Yarn service check fails when
 either resource manager is down in HA enabled cluster
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 23 Nov 2016 16:12:00 -0000


    [ https://issues.apache.org/jira/browse/AMBARI-18929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15690568#comment-15690568 ] 

Tim Thorpe commented on AMBARI-18929:
-------------------------------------

Assuming the python issues are fixed with HDFS and YARN, the status of the service should be properly reported at least since 2.4

https://issues.apache.org/jira/browse/AMBARI-14496

> Yarn service check fails when either resource manager is down in HA enabled cluster
> -----------------------------------------------------------------------------------
>
>                 Key: AMBARI-18929
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18929
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.4.0
>            Reporter: Weiwei Yang
>
> When HA is enabled, yarn service_check.py fails if one of RM is down, even the other one is active. This gives user the wrong impression the yarn cluster is not healthy. Instead, service check should pass, or at least pass with warning that lets user know there is one RM down.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)