ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-12486) Enabling namenode HA fails when non default ports are used
Date Wed, 14 Oct 2015 23:49:05 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-12486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14958029#comment-14958029
] 

Hudson commented on AMBARI-12486:
---------------------------------

FAILURE: Integrated in Ambari-branch-2.1 #683 (See [https://builds.apache.org/job/Ambari-branch-2.1/683/])
AMBARI-12486. Enabling namenode HA fails when non default ports are (jaimin: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=440e2029dcae478b44b6dcec2fe351061abf6d61])
* ambari-web/app/controllers/main/admin/highAvailability/nameNode/step3_controller.js


> 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)

Mime
View raw message