You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Dmytro Sen (JIRA)" <ji...@apache.org> on 2015/12/31 15:56:49 UTC
[jira] [Commented] (AMBARI-14532) AMS fails to stay up after
changing AMS configs to distributed mode
[ https://issues.apache.org/jira/browse/AMBARI-14532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15075987#comment-15075987 ]
Dmytro Sen commented on AMBARI-14532:
-------------------------------------
Committed to trunk and branch-2.2
> 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)