Fix race condition in skipEntries that moves readPosition and markDeletePosition incorrectly - #1478
Merged
Merged
Conversation
…etePosition incorrectly
Contributor
|
Fix looks good, is it easy to reproduce this issue? Would it happen by having a thread acking messages and then other thread calling reset cursor? |
Contributor
Author
that's correct. skipping entries and acking happens in different thread. |
sschepens
pushed a commit
to sschepens/pulsar
that referenced
this pull request
Sep 5, 2019
…etePosition incorrectly (apache#1478)
sschepens
pushed a commit
to sschepens/pulsar
that referenced
this pull request
Sep 5, 2019
…etePosition incorrectly (apache#1478)
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Motivation
If we try to skipEntries for a cursor then first it derives
markDeletePositionand then asynchronously it tries tosetAcknowledgedPositionwhere first it setsreadPosition(advance thereadPositionifnew markDeletePositionis higher than it) and then it again calculatesmarkDeletePositionwith newindividualDeletedMessages. Now, ifindividualDeletedMessageshas been changed since lastmarkDeletePositionis calculated then it makesmarkDeletePositionhigher thanreadPositionwhich creates below exception and it causes failure while fetching stats of the broker.Modifications
sets
readPositionin the last after calculatingmarkDeletePosition.Result
It fixes above exception while skipping entries.