-
Notifications
You must be signed in to change notification settings - Fork 285
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[FIXED] Clustering: possible wrong pending count
This is a regression introduced by PR #1213 which is in v0.23.0 (the latest release). When a queue subscription left the group and its last_sent was the same than the group's last_sent, the remaining queue member should have its last_sent updated. To do that, the replication of a "sent" event for this sequence was issued, which was wrong since it would possibly add a pending on the remaining queue sub. Moreover, this did not account for last_sent being 0, which with the aforementioned behavior, a "sent" of sequence 0 would be replicated causing the remaining queue sub to show a pending_count of 1. The fix for both wrong pending_count and original last_sent issue is to have all nodes (leader and followers) detect that when a member is removed, if that member's last_sent value was the one of the queue group, then update the runtime version of the remaining queue member. Signed-off-by: Ivan Kozlovic <ivan@synadia.com>
- Loading branch information
Showing
2 changed files
with
185 additions
and
112 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters