You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Yusaku Sako (JIRA)" <ji...@apache.org> on 2013/09/10 20:29:52 UTC
[jira] [Commented] (AMBARI-3166) Service Component metrics are
misleading with multiple namenodes in HA
[ 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