[v26.1.x] kafka/server: cap fetch memory allocation at max message size limit - #30313
Merged
ballard26 merged 1 commit intoMay 12, 2026
Merged
Conversation
Use kafka_max_message_size_upper_limit_bytes to clamp max_bytes and max_batch_size in fetch memory allocation instead of the full shard fetch memory budget. This prevents a single partition with an inflated max.message.bytes (e.g. UINT32_MAX) from monopolizing the entire shard's fetch memory, which can starve other partitions and cause fetch timeouts. (cherry picked from commit 2b2c4b3)
ballard26
approved these changes
May 12, 2026
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.
Backport of PR #30023