ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-15601) HA Namenode Move failed on Delete disabled NameNode+ZKFC stage
Date Tue, 29 Mar 2016 03:00:28 GMT

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

Hudson commented on AMBARI-15601:
---------------------------------

SUCCESS: Integrated in Ambari-trunk-Commit #4553 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4553/])
AMBARI-15601: HA Namenode Move failed on Delete disabled NameNode+ZKFC (akovalenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=be444cc145edd6f58d5e43c28fbfef3bffb06e98])
* ambari-web/app/controllers/main/service/reassign/step6_controller.js
* ambari-web/app/messages.js
* ambari-web/app/controllers/main/admin/highAvailability/progress_controller.js
* ambari-web/app/routes/reassign_master_routes.js
* ambari-web/app/controllers/main/service/reassign_controller.js
* ambari-web/test/controllers/main/service/reassign/step6_controller_test.js
* ambari-web/app/mixins/wizard/wizardProgressPageController.js


> 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, AMBARI-15601_branch-2.2.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)

Mime
View raw message