You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Zhiguo Wu (Jira)" <ji...@apache.org> on 2022/10/25 16:11:00 UTC
[jira] [Updated] (AMBARI-25199) Ambari does not update "dfs.namenode.lifeline.rpc-address" during Namenode move operation
[ https://issues.apache.org/jira/browse/AMBARI-25199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zhiguo Wu updated AMBARI-25199:
-------------------------------
Fix Version/s: 2.8.0
> 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
> Fix For: 2.8.0
>
> Time Spent: 1h 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
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ambari.apache.org
For additional commands, e-mail: issues-help@ambari.apache.org