[STORM-2044] Nimbus should not make assignments crazily when Pacemaker goes down and up

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.0.2
• Component/s: storm-core
• Labels: patch
• Environment: CentOS 6.5
• Flags: Important
• Assignee: Unassigned
• Reporter: Danny Chen
• Created: 18/Aug/16 03:59
• Updated: 03/Jul/17 14:57

Description

Now pacemaker is a stand-alone service and no HA is supported. When it goes down, all the workers's heartbeats will be lost. It will take a long time to recover even if pacemaker goes up immediately if there are dozens GB of heartbeats. During the time worker heartbeats are not restored completely, Nimbus will think these workers are dead because of heartbeats timeout and reassign these "dead" workers continuously until heartbeats restore to normal. So, during recovery time, many topologies will be reassigned continuously and the throughout will goes very down.
This is not acceptable.
So i think, pacemaker is not suitable for production if the problem above exists.
i think several ways to solve this problem:
1. pacemaker HA
2. when pacemaker does down, notice nimbus not to reassign any more until it recover