Skip to content

Fix partition index conflict in stream SAC coordinator #13857

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
May 6, 2025

Conversation

acogoluegnes
Copy link
Contributor

Consumers with a same name, consuming from the same stream should have the same partition index. This commit adds a check to enforce this rule and make the subscription fail if it does not comply.

Fixes #13835

Consumers with a same name, consuming from the same stream should have
the same partition index. This commit adds a check to enforce this rule
and make the subscription fail if it does not comply.

Fixes #13835
@acogoluegnes acogoluegnes force-pushed the stream-coordinator-fix-partition-index-conflict branch from 0c99f5a to cad8b70 Compare May 6, 2025 14:12
@acogoluegnes acogoluegnes marked this pull request as ready for review May 6, 2025 14:24
@acogoluegnes acogoluegnes requested a review from kjnilsson May 6, 2025 14:24
@acogoluegnes acogoluegnes merged commit 8cc26c4 into main May 6, 2025
3 checks passed
@acogoluegnes acogoluegnes deleted the stream-coordinator-fix-partition-index-conflict branch May 6, 2025 15:16
michaelklishin added a commit that referenced this pull request May 7, 2025
Fix partition index conflict in stream SAC coordinator (backport #13857)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Stream single active consumer coordinator crashes with plain SAC consumer and a stream consumer at the same time
2 participants
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy