[
https://issues.apache.org/jira/browse/AMBARI-12486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14957889#comment-14957889
]
Juanjo Marron commented on AMBARI-12486:
----------------------------------------
Thanks Jaimin!
> Enabling namenode HA fails when non default ports are used
> ----------------------------------------------------------
>
> Key: AMBARI-12486
> URL: https://issues.apache.org/jira/browse/AMBARI-12486
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, ambari-web
> Affects Versions: 2.1.0, trunk
> Reporter: Juanjo Marron
> Assignee: Juanjo Marron
> Fix For: 2.1.3
>
> Attachments: AMBARI-12486.patch
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
