[
https://issues.apache.org/jira/browse/AMBARI-14532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15076022#comment-15076022
]
Hudson commented on AMBARI-14532:
---------------------------------
ABORTED: Integrated in Ambari-trunk-Commit #4112 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4112/])
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=52ca9daa68b8302775dd2ee8d0b901d53ce69df7])
*
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)
