Hi Juanjo, This is a bug that should be fixed. Thanks for pointing this out. Would you like to go ahead and file a JIRA for this?
Thanks, Yusaku From: Juanjo Marron <[email protected]<mailto:[email protected]>> Reply-To: Ambari User <[email protected]<mailto:[email protected]>>, Juanjo Marron <[email protected]<mailto:[email protected]>> Date: Thursday, July 2, 2015 11:56 AM To: Ambari User <[email protected]<mailto:[email protected]>> Subject: Enabling namenode HA fails when non default ports are used Hi all, I have a question related with High Availability configuration when changing default ports I 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 the port is hardcoded ex: ... this.setConfigInitialValue(config,zooKeeperHosts[0] + ':2181,' + zooKeeperHosts[1] + ':2181,' + zooKeeperHosts[2] + ':2181'); ... Is there any reason to not looking actual port number and use the default value? Thanks for your answer, Regards, Juanjo Marron
