You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ambari.apache.org by "Jaimin Jetly (JIRA)" <ji...@apache.org> on 2016/11/09 00:06:59 UTC

[jira] [Updated] (AMBARI-18220) Namenode start failed on moving namenode on a HA cluster

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

Jaimin Jetly updated AMBARI-18220:
----------------------------------
    Affects Version/s:     (was: 2.4.0)
                       2.1.2

> Namenode start failed on moving namenode on a HA cluster 
> ---------------------------------------------------------
>
>                 Key: AMBARI-18220
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18220
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.1.2
>            Reporter: Jaimin Jetly
>            Assignee: Jaimin Jetly
>            Priority: Critical
>              Labels: 240RMApproved
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-18220.patch
>
>
> *STR:*
> 1. Enable NameNode HA
> 2. Launch "move namendode" wizard
> *Actual Result:* On the page "Configure Component" at the step to start namenode, both namenodes are started. This leads to failure of the request intermittently
> *Expected Result:* Only one namenode "the one which is not being moved" should be started



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