Bound decompressed record size (#23429) - #23449
Merged
Merged
Conversation
The fix improves validation and handling of record sizes across the broker's record processing paths. A new configurable broker/topic-level setting, max.decompressed.message.bytes, allows operators to control the maximum permitted decompressed record size. The limit is applied consistently during produce validation, log compaction and timestamp-based list offsets lookups. Existing APIs remain backward compatible with safe default behavior for callers that do not explicitly configure a limit. Reviewers: Chia-Ping Tsai <chia7712@gmail.com> (cherry picked from commit 4d781f5) (cherry picked from commit a544dc8effd8f1bf90c5746130c91b2a8127e9db) (cherry picked from commit c9cea9f564195771e72f1c9a2c68059bb044e599)
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
3 participants
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.
The fix improves validation and handling of record sizes across the
broker's record processing paths.
A new configurable broker/topic-level setting,
max.decompressed.message.bytes, allows operators to control the maximum
permitted decompressed record size. The limit is applied consistently
during produce validation, log compaction and timestamp-based list
offsets lookups.
Existing APIs remain backward compatible with safe default behavior for
callers that do not explicitly configure a limit.
Reviewers: Chia-Ping Tsai chia7712@gmail.com (cherry picked from
commit 4d781f5) (cherry picked from
commit a544dc8effd8f1bf90c5746130c91b2a8127e9db) (cherry picked from
commit c9cea9f564195771e72f1c9a2c68059bb044e599)