ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jaimin D Jetly (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-18220) Namenode start failed on moving namenode on a HA cluster
Date Sun, 21 Aug 2016 02:23:20 GMT

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

Jaimin D Jetly updated AMBARI-18220:
------------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

+1 received on reviewboard.
Patch committed to trunk and branch-2.4

> 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.4.0
>            Reporter: Jaimin D Jetly
>            Assignee: Jaimin D 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)

Mime
View raw message