You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Aleksandr Kovalenko (JIRA)" <ji...@apache.org> on 2016/03/28 18:44:25 UTC

[jira] [Commented] (AMBARI-15601) HA Namenode Move failed on Delete disabled NameNode+ZKFC stage

    [ https://issues.apache.org/jira/browse/AMBARI-15601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15214448#comment-15214448 ] 

Aleksandr Kovalenko commented on AMBARI-15601:
----------------------------------------------

10487 tests complete (14 seconds)
121 tests pending


> HA Namenode Move failed on Delete disabled NameNode+ZKFC stage
> --------------------------------------------------------------
>
>                 Key: AMBARI-15601
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15601
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.0.0
>            Reporter: Aleksandr Kovalenko
>            Assignee: Aleksandr Kovalenko
>            Priority: Critical
>             Fix For: 2.2.2
>
>         Attachments: AMBARI-15601.patch
>
>
> *STR:*
> # On Nn ha environment, nn1 is on host1 and nn2 is on host2
> # Put host1 in maintenance mode 
> # Start "Move namenode wizard"
> # Wizard will fail on last step "Delete disabled namenode+zkfc" because the namenode to be deleted which was in maintenace mode never stopped as part of wizard, and delete operation on a component in 'STARTED' state throws an exception
> # user ends up with 3 instances of namenode.
> It is reasonable to expect that the source host is in maintenance mode (the user is likely doing a move because the host is in bad state).



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