[ https://issues.apache.org/jira/browse/AMBARI-15803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sebastian Toader updated AMBARI-15803: -------------------------------------- Attachment: (was: AMBARI-15803.branch-2.2.v1.patch) > 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.v2.patch, > AMBARI-15803.trunk.v2.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)