Skip to content

Re-evaluate stream SAC group after connection down event (backport #13657) (backport #13659) #13660

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 31, 2025

Conversation

mergify[bot]
Copy link

@mergify mergify bot commented Mar 31, 2025

The same connection can contain several consumers belonging to a SAC group (group key = vhost + stream + consumer name). The whole new group must be re-evaluated to select a new active consumer after the consumers of the down connection are removed from it.

The previous behavior would not re-evaluate the new group and could select a consumer from the down connection, letting the group with only inactive consumers, as the selected active consumer would never receive the activation message from the stream SAC coordinator.

This commit fixes this problem by removing the consumers of the down down connection from the affected groups and then performing the appropriate operations for the groups to keep on consuming (e.g. notifying an active consumer that it needs to step down).

References #13372


This is an automatic backport of pull request #13657 done by Mergify.
This is an automatic backport of pull request #13659 done by Mergify.

The same connection can contain several consumers belonging to a SAC
group (group key = vhost + stream + consumer name). The whole new group
must be re-evaluated to select a new active consumer after the consumers
of the down connection are removed from it.

The previous behavior would not re-evaluate the new group and could
select a consumer from the down connection, letting the group with only
inactive consumers, as the selected active consumer would never receive
the activation message from the stream SAC coordinator.

This commit fixes this problem by removing the consumers of the down
down connection from the affected groups and then performing the
appropriate operations for the groups to keep on consuming (e.g.
notifying an active consumer that it needs to step down).

References #13372

(cherry picked from commit 602b6ac)
(cherry picked from commit d439b8b)
@acogoluegnes acogoluegnes added this to the 4.0.8 milestone Mar 31, 2025
@acogoluegnes acogoluegnes merged commit 85cb9fd into v4.0.x Mar 31, 2025
270 checks passed
@acogoluegnes acogoluegnes deleted the mergify/bp/v4.0.x/pr-13659 branch March 31, 2025 18:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant