- 最新
- 投票最多
- 评论最多
I think that sittings has to be for the consumer. Can you check if this article is helpful: https://learn.conduktor.io/kafka/how-to-send-large-messages-in-apache-kafka/
Can you try for the broker-side setting message.max.bytes instead?
Hi,
Look at this page to see all MSK parameters you can configure: https://docs.aws.amazon.com/msk/latest/developerguide/msk-configuration-properties.html
Is message.max.bytes a partial solution to your question?
Best,
Didier
Unfortunately not.
Here we go,
$ kafka/bin/kafka-configs.sh --bootstrap-server $b --command-config config/client_iam.properties --entity-type brokers --entity-name 1 --describe --all |grep fetch.max.bytes fetch.max.bytes=57671680 sensitive=false synonyms={DEFAULT_CONFIG:fetch.max.bytes=57671680}
This IS in fact broker level configuration supported by Kafka broker behind MSK, but MSK Cluster Configuration setup indeed doesn't allow this property to be overridden.
Could you please share your use case for us to to have more information and justification for having fetch request size over 50 MB? Please respond as a comment to this answer.
已回答 2 年前
In short the use case is to increase consumer throughput for data backfill scenarios.
相关内容
- AWS 官方已更新 7 个月前

It's definitely a broker config too - see the link to the Kafka documentation in the question.