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.
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
KAFKA-10188: Prevent SinkTask::preCommit from being called after SinkTask::stop #8910
KAFKA-10188: Prevent SinkTask::preCommit from being called after SinkTask::stop #8910
Changes from all commits
9e5b217
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Shouldn't this be volatile?
Yes, it's true that
WorkerSinkTask.close()
is always and only called from within theWorkerTask.doRun()
after the tasks determines it will stop. However, theonPartitionsRevoked(...)
method is called from the consumer thread, and making the field volatile is the only way to ensure that the consumer thread reads a non-cached value.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.
The Javadocs for the
ConsumerRebalanceLister
state that the callback "will only execute in the user thread as part of thepoll(long)
call"; I think we have a guarantee here thatonPartitionsRevoked
will be called on the same thread that setstaskStopped
tofalse
. A fun way to verify this is to view the exceptions that get thrown by this bug; the stack traces include these lines:The only edge case I can think of might be with asynchronous offset commits, but fwict those don't trigger asynchronous rebalance listener callbacks (if they trigger rebalances or rebalance listener callbacks at all).
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.
Verified locally that this test fails when the additions to the
onPartitionsRevoked(...)
method above are removed locally. Nice work, @C0urante.