You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by Juanjo Marron <jm...@us.ibm.com> on 2015/08/20 01:59:46 UTC
Review Request 37626: AMBARI-12486 Enabling namenode HA fails when non
default ports are used
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/37626/
-----------------------------------------------------------
Review request for Ambari and Yusaku Sako.
Repository: ambari
Description
-------
Enabling HA code may not read correct properties.
When HDFS and ZOOKEEPER ports are changed (different than default values ZK: 2181 and HDFS: 8020,50070,50470), HA wizard menus is still showing the ones by default and HA namenode fails with connection errors.
Checked the source code for the Step 3 in namenode HA wizard (ambari-web/app/controllers/main/admin/highAvailability/nameNode/step3_controller.js)
The node address is looked from the configuration but ports hardcoded instead of the new once modified on the installation wizard, ex:
...
this.setConfigInitialValue(config,'qjournal://' + journalNodeHosts[0] + ':8485;' + journalNodeHosts[1] + ':8485;' + journalNodeHosts[2] + ':8485/' + nameServiceId);
this.setConfigInitialValue(config,zooKeeperHosts[0] + ':2181,' + zooKeeperHosts[1] + ':2181,' + zooKeeperHosts[2] + ':2181');
...
This is a bug that should be fixed.
Diffs
-----
ambari-web/app/controllers/main/admin/highAvailability/nameNode/step3_controller.js cf2d971
Diff: https://reviews.apache.org/r/37626/diff/
Testing
-------
Manual test on fresh installation
Thanks,
Juanjo Marron