[jira] [Created] (AMBARI-14814) Ambari not showing active/standby status for NameNodes when custom ports are used

["Vitaly Brodetskyi (JIRA)" <ji...@apache.org>]

Vitaly Brodetskyi created AMBARI-14814:
------------------------------------------

             Summary: 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


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)