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

Posted to dev@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2014/11/18 02:06:33 UTC

[jira] [Commented] (AMBARI-8360) Moving namenode fails if NameNode HA is enabled

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

Hudson commented on AMBARI-8360:
--------------------------------

SUCCESS: Integrated in Ambari-branch-1.7.0 #409 (See [https://builds.apache.org/job/Ambari-branch-1.7.0/409/])
AMBARI-8360. Moving namenode fails if NameNode HA is enabled on HDP-2.2. (Oleg via jaimin) (jaimin: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=df306cfc752d746377f81a30311acfc5ff577683)
* ambari-web/app/controllers/main/service/reassign/step4_controller.js


> Moving namenode fails if NameNode HA is enabled
> -----------------------------------------------
>
>                 Key: AMBARI-8360
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8360
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 1.7.0
>            Reporter: Jaimin D Jetly
>            Assignee: Oleg Nechiporenko
>            Priority: Blocker
>             Fix For: 1.7.0
>
>         Attachments: AMBARI-8360.patch
>
>
> Issue:
> When HA is enabled on a HDP 2.2 cluster and Namenode Move Wizard is used to move the NN to another host - start of services fails because fs.defaultFS points to <host>:port (instead of servicename:port) where hostname is the host of the standby namenode.



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