-
Notifications
You must be signed in to change notification settings - Fork 354
fix(kafka): eliminate Resume timeout race in batch consumer pause/heartbeat #1313
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
Open
absorbb
wants to merge
2
commits into
newjitsu
Choose a base branch
from
fix/kafka-consumer-resume-timeout
base: newjitsu
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Making
resumeChannelbuffered removes the rendezvous semantics that_unpause()currently relies on inpauseOrSuspend()(_unpause(); consumer.Close(); bc.consumer.Store(nil)). With an unbuffered channel,_unpause()blocks until the pause heartbeat loop receives the signal; now it can return immediately while the loop is still insideReadMessage(). Closing the consumer in that window can produce a non-timeout error in the pause loop and triggerrestartConsumerAsync(), which can recreate a consumer right after we intended to suspend it. This looks like a user-visible regression (suspend may turn into restart churn).Can we keep non-blocking
resume()behavior without weakening_unpause()synchronization (e.g. separate channels/paths for resume vs suspend-ack, or an explicit ack/wait primitive for suspend)?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch — fixed in b45169a with the separate-channel approach you suggested.
resume()keeps the bufferedresumeChannel(non-blocking deposit, which is what fixed the Resume timeout). The suspend path now uses a dedicated unbufferedstopChannel:_unpause()sends on it, so the send only completes once the heartbeat has received it and is leaving its loop — i.e. no longer insideReadMessage(). That restores the rendezvouspauseOrSuspendrelies on, soconsumer.Close()no longer races an activeReadMessageand can't triprestartConsumerAsync()into recreating the consumer we just suspended.The heartbeat's
stopChannelcase only setspaused=falseand breaks — no defensiveResume, since the caller is about to close the consumer anyway.