[AMBARI-15126] Move NameNode wizard in HA environment fails to update configs correctly when namenode is not running on default port

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.1.2
• Fix Version/s: 2.5.0
• Component/s: ambari-web
• Labels: namenode
• Flags: Important
• Assignee: Richard Zang
• Reporter: deprecated-se
• Created: 22/Feb/16 09:10
• Updated: 10/Nov/16 03:07
• Resolved: 10/Nov/16 02:48

Description

Condition:
1. hdfs deploy ha
2. "dfs.namenode.http-address" is not set to the default port 50070

Result:
1. Ambari will always substitute configures relative to "nn2"
2. The active "Move Namenode" failed and make configure inconsistent, the cluster crashes

Code location:

ambari-web/app/controllers/main/service/reassign/step4_controller.js

if (App.get('isHaEnabled')) {
      var nameServices = configs['hdfs-site']['dfs.nameservices'];
      var suffix = (configs['hdfs-site']['dfs.namenode.http-address.' + nameServices + '.nn1'] === sourceHostName + ':50070') ? '.nn1' : '.nn2';
      configs['hdfs-site']['dfs.namenode.http-address.' + nameServices + suffix] = targetHostName + ':50070';
      ...
    }

Issue Links

• links to: Review Board