[
https://issues.apache.org/jira/browse/AMBARI-18376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raymond updated AMBARI-18376:
-----------------------------
Labels: patch (was: )
Fix Version/s: 2.2.2
Status: Patch Available (was: Open)
This seems like it should work on 2.4 as well, but not tested.
> Deploying 2 Clusters simultaneously results in one cluster failing.
> -------------------------------------------------------------------
>
> Key: AMBARI-18376
> URL: https://issues.apache.org/jira/browse/AMBARI-18376
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 2.2.2
> Reporter: Raymond
> Priority: Minor
> Labels: patch
> Fix For: 2.2.2
>
>
> Steps to Reproduce:
> 1) Spin up an Ambari server node
> 2) Setup 10 ambari agent nodes
> 3) create 2 blueprints and 2 cluster templates with 5 nodes for each cluster
> (hdfs, zookeeper, yarn)
> 4) Upload both blueprints using the ambari api
> 5) Upload both cluster templates using the ambari api
> One cluster will fail, ssh into one of the nodes (with a zookeeper server) on
> the failed cluster.
> Find the zoo.cfg file in /etc/zookeeper (find /etc/zookeeper -name zoo.cfg)
> Actual: cat the zoo.cfg, notice all hostnames of both clusters are in this
> file
> Expected: zoo.cfg should contain only the hostnames defined for this cluster.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
