[
https://issues.apache.org/jira/browse/AMBARI-8360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14215566#comment-14215566
]
Hudson commented on AMBARI-8360:
--------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit-docker #255 (See
[https://builds.apache.org/job/Ambari-trunk-Commit-docker/255/])
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=a7f832097362d33e47db10732ac040391ec3557d)
* 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)
