You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Vitaly Brodetskyi (JIRA)" <ji...@apache.org> on 2014/07/10 18:06:06 UTC

[jira] [Updated] (AMBARI-6455) On cluster with HA enabled, SNameNode state via api is "STARTED"

     [ https://issues.apache.org/jira/browse/AMBARI-6455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vitaly Brodetskyi updated AMBARI-6455:
--------------------------------------

    Attachment: AMBARI-6455.patch

> On cluster with HA enabled, SNameNode state via api is "STARTED"
> ----------------------------------------------------------------
>
>                 Key: AMBARI-6455
>                 URL: https://issues.apache.org/jira/browse/AMBARI-6455
>             Project: Ambari
>          Issue Type: Task
>          Components: agent
>            Reporter: Vitaly Brodetskyi
>            Assignee: Vitaly Brodetskyi
>             Fix For: 1.7.0
>
>         Attachments: AMBARI-6455.patch
>
>
> *Steps to reproduce:*
> 1. Enable HA
> 2. Call API
> {noformat}http://<server>:8080/api/v1/clusters/cl1/services?fields=components/ServiceComponentInfo{noformat}
> *Expected result:*
> At least "state" shouldn't be "STARTED"
> It returns that there are NameNode and SecondaryNameNode on cluster.
> I guess that SecondaryNameNode may refer to added NameNode (I don't know actually). But in any case both of them have "state" : "STARTED" which is weird.



--
This message was sent by Atlassian JIRA
(v6.2#6252)