You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2016/02/01 20:10:39 UTC
[jira] [Commented] (AMBARI-14814) Ambari not showing active/standby
status for NameNodes when custom ports are used
[ https://issues.apache.org/jira/browse/AMBARI-14814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15126817#comment-15126817 ]
Hudson commented on AMBARI-14814:
---------------------------------
SUCCESS: Integrated in Ambari-branch-2.2 #277 (See [https://builds.apache.org/job/Ambari-branch-2.2/277/])
AMBARI-14814. Ambari not showing active/standby status for NameNodes (vbrodetskyi: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=5fae3f5b5f9258c8a2bec425574876684e4e0b2b])
* ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AbstractProviderModule.java
* ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/JMXPropertyProviderTest.java
* ambari-server/src/main/java/org/apache/ambari/server/controller/jmx/JMXHostProvider.java
* ambari-server/src/test/java/org/apache/ambari/server/controller/internal/JMXHostProviderTest.java
* ambari-server/src/main/java/org/apache/ambari/server/controller/jmx/JMXPropertyProvider.java
> Ambari not showing active/standby status for NameNodes when custom ports are used
> ---------------------------------------------------------------------------------
>
> Key: AMBARI-14814
> URL: https://issues.apache.org/jira/browse/AMBARI-14814
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.2.1
> Reporter: Vitaly Brodetskyi
> Assignee: Vitaly Brodetskyi
> Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-14814.patch
>
>
> Steps:
> Deployed cluster via UI.
> Enabled NameNode HA.
> Enabled ResourceManager HA.
> Changed ports to custom (38088) for "yarn.resourcemanager.webapp.address.rm1" and "yarn.resourcemanager.webapp.address.rm2" properties.
> Restarted all services, required it.
> Enabled NameNodeHA.
> Changed ports to custom (38088) for
> dfs.namenode.http-address.nameservice.nn1
> dfs.namenode.http-address.nameservice.nn2
> dfs.namenode.https-address.nameservice.nn1
> dfs.namenode.https-address.nameservice.nn2
> dfs.namenode.rpc-address.nameservice.nn1
> dfs.namenode.rpc-address.nameservice.nn2
> properties.
> Restarted all services, required it.
> Result: Ambari is not showing which NameNode is active and which one is standby.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)