[
https://issues.apache.org/jira/browse/AMBARI-25199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16795927#comment-16795927
]
Hudson commented on AMBARI-25199:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #723 (See
[https://builds.apache.org/job/Ambari-branch-2.6/723/])
AMBARI-25199. Ambari does not update "dfs.namenode.lifeline.rpc-address"
(github:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=a308fd42a2db2290c47c1d796f1fc575e873cccc])
* (edit) ambari-web/app/utils/configs/move_namenode_config_initializer.js
> Ambari does not update "dfs.namenode.lifeline.rpc-address" during Namenode
> move operation
> -----------------------------------------------------------------------------------------
>
> Key: AMBARI-25199
> URL: https://issues.apache.org/jira/browse/AMBARI-25199
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
> Affects Versions: 2.6.2
> Reporter: Attila Magyar
> Assignee: Attila Magyar
> Priority: Major
> Labels: pull-request-available
> Time Spent: 40m
> Remaining Estimate: 0h
>
> While performing Namenode (NN) move from one host to another. And if
> "dfs.namenode.lifeline.rpc-address" property is set., during the NN move, we
> see that the value associated with the property
> "dfs.namenode.lifeline.rpc-address" that is being moved is not updated.
> Hence, NN would fail to start during restart stage of the NN Move operation.
> This can be reproduced as below,
> 1. Have a HDFS HA cluster.
> 2. Make sure "dfs.namenode.lifeline.rpc-address" is set for both the NNs.
> 3. Perform the NN move operation from any NN to new host.
> 4. Observe NN failure to startup during restart phase
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
