diff options
| author | Matthias Radestock <matthias@rabbitmq.com> | 2014-04-13 19:45:06 +0100 |
|---|---|---|
| committer | Matthias Radestock <matthias@rabbitmq.com> | 2014-04-13 19:45:06 +0100 |
| commit | d9f1c1b064708d94e4bbcaea885cfcadf51c9b11 (patch) | |
| tree | 1209dbfa8083b28b2467791085b3b7c13abdf7bb /packaging | |
| parent | 56f423fcbe7c9a67a92de2a86cfdee02bb29e927 (diff) | |
| download | rabbitmq-server-git-d9f1c1b064708d94e4bbcaea885cfcadf51c9b11.tar.gz | |
ensure propagation of master death
Previously slaves were monitoring the master and sending a
process_death message through gm in an attempt to get the updated gm
state propagated (and thus members_changed callbacks getting invoked
on slaves, which in turn trigger promotion).
However, the DOWN notification for the master may well arrive and be
processed, and the process_death message sent around the ring, before
GM has noticed the master death, thus rendering the process_death
broadcast ineffectual for its intended purpose.
With the recent GM changes we can guarantee that at least one slave
will be notified of the master death via GM. So we emit the
process_death message then, and not on master DOWN (and ditch the
master monitoring as a result). Since the new emission is triggered by
a gm notification we know GM is aware of the master death, thus
avoiding the aforementioned problem.
Diffstat (limited to 'packaging')
0 files changed, 0 insertions, 0 deletions
