org.apache.kafka.common.errors.RecordTooLargeException: The request included a message larger than the max message size the server will accept.
Java client tuning: Max_ REQUEST_ SIZE_ CONFIG
Kafka server side adjustment: message. Max. bytes = 2147483640 is close to the max of int, because the maximum range of this value is int
Special note: after the parameter is adjusted, it has no effect on the created topic
adjust the parameter of the created topic: set to the maximum integer value of 2147483647
bin/kafka-configs.sh --zookeeper localhost:2181 --alter --topic topic_name --add-config max.message.bytes=2147483647Problem solving
Read More:
- TIDB-kafka server: Message was too large, server rejected it to avoid allocation error
- Flume monitors a single append file in real time
- The file server reports an error of 413, and the file uploaded by nginx reports an error of 413 request entity too large
- The sparse matrix of R language is too large to be used as.matrix
- mysql5.7.26：[ERR] 1118 – Row size too large (＞ 8126)
- Nginx upload error 413 request entity too large
- Nginx modifies the front end request size limit (413 request entity too large)
- Error in plot.new() : figure margins too large
- Kibana access error: data too large [How to Solve]
- Java long type error: error: integer number too large
- Update project manually_ Solution of too large jar package in springboot
- circuit_breaking_exception,“reason“:“[parent] Data too large, data for [＜http_request＞]
- The icon on the layui page is not displayed, and an error message is reported: Failed to decode downloaded font …..
- SAP mm receives the purchase order and reports an error – table t169p entry znmi does not exist-
- Info:Memory module [DIMM] needs attention: Single-bit warning error rate exceeded, Single-bit fai…
- SAP Migo 101 receives the work order and reports an error – check table tfbefu_ CR entry 10 does not exist – Countermeasures
- An error is reported when logging into mysql. The error message is error 1049 (42000): unknown database ‘XXXXXX’
- Using the TP framework, an error is reported sqlstate [08004] [1040] too many connections
- IIS “Bad Request – Request Too Long. HTTP Error 400. The size of the request headers is too long.”
- Error splitting file: file too large solution