Mailing-List: contact ambari-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ambari-dev@incubator.apache.org
Date: Tue, 10 Sep 2013 18:29:52 +0000 (UTC)
From: "Yusaku Sako (JIRA)" <jira@apache.org>
To: ambari-dev@incubator.apache.org
Message-ID: <JIRA.12667857.1378834911669.109520.1378837792600@arcas>
In-Reply-To: <JIRA.12667857.1378834911669@arcas>
References: <JIRA.12667857.1378834911669@arcas>
Subject: [jira] [Commented] (AMBARI-3166) Service Component metrics are
 misleading with multiple namenodes in HA
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Yusaku Sako commented on AMBARI-3166:
-------------------------------------

+1 for the patch.
                
> Service Component metrics are misleading with multiple namenodes in HA
> ----------------------------------------------------------------------
>
>                 Key: AMBARI-3166
>                 URL: https://issues.apache.org/jira/browse/AMBARI-3166
>             Project: Ambari
>          Issue Type: Bug
>          Components: controller
>    Affects Versions: 1.4.1
>            Reporter: Siddharth Wagle
>            Assignee: Siddharth Wagle
>             Fix For: 1.4.1
>
>         Attachments: AMBARI-3166.patch
>
>
> 1. Installed a cluster with 3 host (ambari server on c6401).
> 2. Enable HA, active NN on c6402, stand by NN on c6401.
> 3. Stop NN on c6402, then c6401 become active. The result of API call (http://c6401.ambari.apache.org:8080/api/v1/clusters/HAactive/services?fields=components/ServiceComponentInfo).
> 4. Stop NN on c6401, Start c6402, then c6402 still be active. 
> The API call results are different. 
> ====================================
> The problem is: 
> In step4, we still have an active NN c6402, but the serviceComponentInfo has nothing. 
> eg, we cannot get NN start time from serviceComponentInfo any longer, this means c6402 is still active and NN heap/rpc .etc properties can be reached from API (and will be shown on UI), BUT NN Uptime is NULL. This does not make sense.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira