You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Antonenko Alexander (JIRA)" <ji...@apache.org> on 2016/02/23 12:58:18 UTC

[jira] [Updated] (AMBARI-14625) NameNode moving fails on trunk

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

Antonenko Alexander updated AMBARI-14625:
-----------------------------------------
    Affects Version/s:     (was: trunk)
                       2.4.0

> NameNode moving fails on trunk
> ------------------------------
>
>                 Key: AMBARI-14625
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14625
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.4.0
>            Reporter: Olivér Szabó
>            Assignee: Antonenko Alexander
>             Fix For: 2.4.0
>
>         Attachments: blueprint.json, branch_2.2-commands.png, branch_2.2-hosts.png, cluster-creation-template.json, trunk-commands.png, trunk-hosts.png
>
>
> On trunk NameNode moving fails at Configure Component page when Ambari tries to start NameNode components. It works properly on 2.2 branch.
> test case: 
> - namenode hosts: c6401, c6403
> - move c6403 namenode to c6402
> The difference between trunk and branch-2.2: 
> on branch 2.2 after moving the namenode, it tries to start namenode on c6401, on trunk it tries to start namenode on c6401 and c6402 too (before the manual commands, which is obviously wrong)



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