KAFKA-20539 Prevent Hot Data Loss on Partition Expansion for Latest Policy#22784
Open
m1a2st wants to merge 3 commits into
Open
KAFKA-20539 Prevent Hot Data Loss on Partition Expansion for Latest Policy#22784m1a2st wants to merge 3 commits into
m1a2st wants to merge 3 commits into
Conversation
github-actions
Bot
added
triage
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
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.
Enhanced the auto.offset.reset documentation in ConsumerConfig.java to
clearly explain the message-loss risk when using latest after increasing
the partition count, and recommended by_duration: as a safer
alternative.
Updated
basic-kafka-operations.mdwith a recommendation section and acomparison table for suitable
<duration>values under both theconsumer (KIP-848) and classic group protocols.