[ 
https://issues.apache.org/jira/browse/STRATOS-600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nirmal Fernando resolved STRATOS-600.
-------------------------------------

    Resolution: Fixed

> A new member to replace a faulty member should be spawned via min-check rule
> ----------------------------------------------------------------------------
>
>                 Key: STRATOS-600
>                 URL: https://issues.apache.org/jira/browse/STRATOS-600
>             Project: Stratos
>          Issue Type: Bug
>            Reporter: Nirmal Fernando
>            Assignee: Nirmal Fernando
>            Priority: Blocker
>             Fix For: 4.0.0 RC1
>
>
> Currently we're starting instances directly upon receiving a member fault 
> event which lead to a synchronization issue with the min-check rule and ended 
> up with spinning up 2 instances.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to