You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@stratos.apache.org by "Nirmal Fernando (JIRA)" <ji...@apache.org> on 2014/04/10 20:08:19 UTC

[jira] [Commented] (STRATOS-600) A new member to replace a faulty member should be spawned via min-check rule

    [ https://issues.apache.org/jira/browse/STRATOS-600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13965629#comment-13965629 ] 

Nirmal Fernando commented on STRATOS-600:
-----------------------------------------

Fixed in a311fc1c8e3289d33f07fac9d1aa2ccbbf817e3c

> 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)