[
https://issues.apache.org/jira/browse/AMBARI-15803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15237039#comment-15237039
]
Sebastian Toader commented on AMBARI-15803:
-------------------------------------------
Committed to trunk:
{code}
commit 2d25706dfb62fb557b6186d0a8c0f512724f39ea
Author: Toader, Sebastian <stoa...@hortonworks.com>
Date: Tue Apr 12 09:27:22 2016 +0200
AMBARI-15803. Restarting ambari-server after successful blueprint deploy of
large cluster makes it unresponsive. (stoader)
{code}
Committed to branch-2.2:
{code}
commit 7e6877a1589be25499d0a833d3099e612d9b420d
Author: Toader, Sebastian <stoa...@hortonworks.com>
Date: Tue Apr 12 09:22:06 2016 +0200
AMBARI-15803. Restarting ambari-server after successful blueprint deploy of
large cluster makes it unresponsive. (stoader)
{code}
> 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)
