Fix: complete MessageReplay immediately if there is no entry to replay which will not block further reads as current Replay is finished #102
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
While doing messageReplay: if all the replay-entries are already acked then Dispatcher was not replaying any entry and also was not receiving a
ReadEntriesCallback
which keepsmessagesToReplay
in pending state and further reads couldn't read next entries.Modifications
If all the replay-entries are already acked
messagesToReplay
bucketmessagesToReplay
flag completeResult
Dispatcher will immediately mark
messagesToReplay
flag complete incase of all invalid-entries for replay and continue reading more messages and consumer will not be blocked while receiving messages.