build(kafka): change message.max.bytes in broker side to align with producer and consumer #5126
Conversation
This file contains 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
agrski
reviewed
Sep 5, 2023
RafalSkolasinski
pushed a commit
that referenced
this pull request
Sep 7, 2023
…roducer and consumer (#5126)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What this PR does / why we need it:
Currently, the Kafka producers and consumers all share the same increased
message.max.bytessetting. However, this is not set at the broker level. This can cause errors when payloads too large get rejected by the broker (e.g. see #5125 ).This PR changes the default value of that setting to align with the config of the producers and consumers - as well as increasing the memory resources allocated to the Kafka broker to account for the new max.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer: