You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Yusaku Sako (JIRA)" <ji...@apache.org> on 2014/11/18 01:23:33 UTC
[jira] [Updated] (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:all-tabpanel ]
Yusaku Sako updated AMBARI-8360:
--------------------------------
Summary: Moving namenode fails if NameNode HA is enabled (was: Moving namenode fails if NameNode HA is enabled on HDP-2.2)
> 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)