Svetoslav Neykov created BROOKLYN-393:
-----------------------------------------
Summary: A failing member on cluster start will get the clustet
stuck in a failed state
Key: BROOKLYN-393
URL: https://issues.apache.org/jira/browse/BROOKLYN-393
Project: Brooklyn
Issue Type: Bug
Reporter: Svetoslav Neykov
A failing member on cluster start sets the cluster in a {{ON_FIRE}} state. The
only way to fix it to do a restart **on the cluster**.
Fail the cluster through the notUp/problems maps through the quorum mechanism.
Always set RUNNING state on cluster start regardless of member states. This
will allow post-start fixes. Restarting the failed member or removing it and
creating a new one in its place.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
