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-14532) AMS fails to stay up after changing AMS configs to distributed mode
Date Thu, 31 Dec 2015 15:35:49 GMT

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

Hudson commented on AMBARI-14532:
---------------------------------

ABORTED: Integrated in Ambari-branch-2.2 #133 (See [https://builds.apache.org/job/Ambari-branch-2.2/133/])
AMBARI-14532 AMS fails to stay up after changing AMS configs to (dsen: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=0683a1ec0540d5ec2c6315ad652d0ed60f86ab54])
* ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-hbase-site.xml


> AMS fails to stay up after changing AMS configs to distributed mode
> -------------------------------------------------------------------
>
>                 Key: AMBARI-14532
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14532
>             Project: Ambari
>          Issue Type: Bug
>          Components: stacks
>    Affects Versions: 2.2.1
>            Reporter: Dmytro Sen
>            Assignee: Dmytro Sen
>            Priority: Blocker
>             Fix For: 2.2.1
>
>         Attachments: AMBARI-14532.patch
>
>
> 1. Bring up a cluster with basic services and Hbase HA enabled
> 2. Change following ams configs:
> Metrics Service operation mode = distributed
> hbase.cluster.distributed = true
> hbase.rootdir = hdfs://nameservice/amshbase
> 3. restart AMS
> 4. Once AMS is started successfully it should stay up and running
> Expected: AMS is up and running
> Actual: AMS fails to stay up.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message