diff options
| author | Anders Svensson <[email protected]> | 2016-02-18 23:01:33 +0100 |
|---|---|---|
| committer | Anders Svensson <[email protected]> | 2016-02-19 01:01:33 +0100 |
| commit | cc4ccfb0756bb563c869d94b630ccfecb571d6c2 (patch) | |
| tree | 178ef293a8c71ccf93902a6fdd0e2453d0778066 /lib/diameter/src/base/diameter_callback.erl | |
| parent | 6759d8fd81d52cdfff5a1c2f788f740d1a4e6f67 (diff) | |
| download | otp-cc4ccfb0756bb563c869d94b630ccfecb571d6c2.tar.gz otp-cc4ccfb0756bb563c869d94b630ccfecb571d6c2.tar.bz2 otp-cc4ccfb0756bb563c869d94b630ccfecb571d6c2.zip | |
Fix handling of shared peer connections in watchdog state SUSPECT
A peer connection shared from a remote node was regarded as being
available for peer selection (aka up) as long as its peer_fsm process
was alive; that is, for the lifetime of the peer connection. In
particular, it didn't take note of transitions into watchdog state
SUSPECT, when the connection remains. As a result, retransmissions could
select the same peer connection whose watchdog transition caused the
retransmission.
A service process now broadcasts a peer_down event just as it
does a peer_up event.
The fault predates the table rearrangements of commit 8fd4e5f4.
Diffstat (limited to 'lib/diameter/src/base/diameter_callback.erl')
0 files changed, 0 insertions, 0 deletions