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

Fix workqueue streams consumers receiving messages that were dropped by stream on limits #5059

Merged
merged 2 commits into from
Feb 11, 2024

Conversation

wallyqs
Copy link
Member

@wallyqs wallyqs commented Feb 11, 2024

No description provided.

@wallyqs wallyqs requested a review from a team as a code owner February 11, 2024 18:02
Signed-off-by: Waldemar Quevedo <wally@nats.io>
@derekcollison derekcollison force-pushed the workqueue-consumer-discard-new branch from 4a648f3 to f7b3e40 Compare February 11, 2024 18:22
…ax bytes set, we need to do those checks before proposing the message.

The reason is that the consumer ack flow will be async state and some replicas might accept the message where others would not based on limits.

Signed-off-by: Derek Collison <derek@nats.io>
@derekcollison derekcollison force-pushed the workqueue-consumer-discard-new branch from f7b3e40 to 9a496ed Compare February 11, 2024 18:22
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 b2d37d7 into main Feb 11, 2024
4 checks passed
@derekcollison derekcollison deleted the workqueue-consumer-discard-new branch February 11, 2024 18:51
wallyqs added a commit that referenced this pull request Feb 14, 2024
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