Skip to content
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

[FIXED] LeafNodes: Queue interest may be lost in super cluster #6377

Merged
merged 1 commit into from
Jan 16, 2025

Conversation

kozlovic
Copy link
Member

If a cluster has leafnode connections and each have the same queue group, the loss of a leafnode connection could cause the server in the "hub" cluster to drop interest across a gateway for this queue group.

The issue is fixed by properly accounting for all queue sub and unsub in the server gateway interest map.

Signed-off-by: Ivan Kozlovic [email protected]

If a cluster has leafnode connections and each have the same queue
group, the loss of a leafnode connection could cause the server
in the "hub" cluster to drop interest across a gateway for this
queue group.

The issue is fixed by properly accounting for all queue sub and
unsub in the server gateway interest map.

Signed-off-by: Ivan Kozlovic <[email protected]>
@kozlovic kozlovic requested a review from a team as a code owner January 16, 2025 01:15
Copy link
Member

@derekcollison derekcollison left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@derekcollison derekcollison merged commit 39b840f into main Jan 16, 2025
5 checks passed
@derekcollison derekcollison deleted the fix_interest_leaf_route_gw branch January 16, 2025 01:44
neilalexander added a commit that referenced this pull request Jan 22, 2025
Includes the following:

- #6373
- #6377
- #6379
- #6390
- #6392
- #6387
- #6292

Signed-off-by: Neil Twigg <[email protected]>
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.

2 participants