Github user danny0405 commented on the issue:
https://github.com/apache/storm/pull/838
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
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
