ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Juanjo Marron (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (AMBARI-12486) Enabling namenode HA fails when non default ports are used
Date Thu, 23 Jul 2015 22:02:04 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-12486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Juanjo Marron reassigned AMBARI-12486:
--------------------------------------

    Assignee: Juanjo Marron  (was: Yusaku Sako)

> 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, 2.1.1, 2.1.2
>            Reporter: Juanjo Marron
>            Assignee: Juanjo Marron
>
> 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)

Mime
View raw message