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

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 4.0.0
• Assignee: Nirmal Fernando
• Reporter: Nirmal Fernando
• Created: 10/Apr/14 18:04
• Updated: 10/Apr/14 18:07
• Resolved: 10/Apr/14 18:07

Description

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.