[log] Introduce OffsetForLeaderEpoch Request/Response #788
Conversation
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
2 tasks
swuferhong
changed the title
Contributor
Author
|
@wuchong pr ready, could you take a look at this pr? thx. |
swuferhong
force-pushed
the
offsets-for-leader-epoch
branch
from
fed731a to
3579faf
Compare
swuferhong
force-pushed
the
offsets-for-leader-epoch
branch
from
3579faf to
112c547
Compare
polyzos
force-pushed
the
main
branch
3 times, most recently
from
d88c76c to
434a4f4
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Purpose
Linked issue: #750
To use LeaderEpoch rather than HighWatermark for truncation, we need to introduce OffsetForLeaderEpochRequest/Response to fetch the latest LeaderEpoch -> Offset info from leader to truncate log.
Brief change log
Tests
API and Format
Documentation