ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-14814) Ambari not showing active/standby status for NameNodes when custom ports are used
Date Wed, 27 Jan 2016 19:58:39 GMT

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

Hadoop QA commented on AMBARI-14814:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12784666/AMBARI-14814.patch
  against trunk revision .

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/5082//console

This message is automatically generated.

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

Mime
View raw message