fix: lower max msg byte in docker to allow us to test against kafka 4.0 #1392
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
|
If it is not enough, you can try to reduce it further (e.g. 1MB) and you can also reduce the number of partitions with offsets.topic.num.partitions. It is 50 by default. 5 may be enough for your tests. |
petedannemann
changed the title
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.
Kafka 4.0 currently runs out of memory when a high max message size is used, lowering this allows us to test against Kafka 4.0 in CI #1360 (comment)
For consistency I have done this everywhere for all Kafka versions we test against. It was probably a mistake to make it so large from the start