[
https://issues.apache.org/jira/browse/AMBARI-15803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15236887#comment-15236887
]
Hudson commented on AMBARI-15803:
---------------------------------
SUCCESS: Integrated in Ambari-branch-2.2 #622 (See
[https://builds.apache.org/job/Ambari-branch-2.2/622/])
AMBARI-15803. Restarting ambari-server after successful blueprint deploy
(stoader:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=7e6877a1589be25499d0a833d3099e612d9b420d])
*
ambari-server/src/test/java/org/apache/ambari/server/topology/LogicalRequestTest.java
*
ambari-server/src/main/java/org/apache/ambari/server/topology/LogicalRequest.java
> Restarting ambari-server after successful blueprint deploy of large cluster
> makes it unresponsive
> -------------------------------------------------------------------------------------------------
>
> Key: AMBARI-15803
> URL: https://issues.apache.org/jira/browse/AMBARI-15803
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.2.2
> Reporter: Sebastian Toader
> Assignee: Sebastian Toader
> Priority: Blocker
> Fix For: 2.2.2
>
> Attachments: AMBARI-15803.branch-2.2.v3.patch,
> AMBARI-15803.trunk.v3.patch
>
>
> If a cluster is being provisioned using Blueprint then Ambari server
> restarted prior all hosts specified in the cluster creation template was
> assigned to the cluster, than the server becomes unresponsive unable to load
> the cluster from database and continue the cluster creation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
