【 TiDB 使用环境】
5.7.25-TiDB-v4.0.6
【概述】：binlog架构，写kafka是报 消息体过大；fail to produce message to kafka, please check the state of kafka server"] [error=“kafka: Failed to produce message to topic feature_binlog: kafka server: Message was too large, server rejected it to avoid allocation error.”
但业务侧 写了很多日志，很难定位和限制大消息体的发生；这个drainer端报错可以更详细些吗？比如有主键或者唯一性约束的打印对应的字段值？
【背景】：做过哪些操作
【现象】：业务和数据库现象
【问题】：当前遇到的问题
【业务影响】：
【TiDB 版本】：5.7.25-TiDB-v4.0.6
【附件】：
- 相关日志 [FATAL] [kafka.go:223] [“fail to produce message to kafka, please check the state of kafka server”] [error=“kafka: Failed to produce message to topic feature_binlog: kafka server: Message was too large, server rejected it to avoid allocation error.”] [stack=“github.com/pingcap/log.Fatal\ \t/home/jenkins/agent/workspace/build_binlog_multi_branch_v4.0.6/go/pkg/mod/github.com/pingcap/log@v0.0.0-20200117041106-d28c14d3b1cd/global.go:59\ github.com/pingcap/tidb-binlog/drainer/sync.(*KafkaSyncer).run.func2\ \t/home/jenkins/agent/workspace/build_binlog_multi_branch_v4.0.6/go/src/github.com/pingcap/tidb-binlog/drainer/sync/kafka.go:223”]
- 配置文件
message.max.bytes=10485760
eplica.fetch.max.bytes=10485760
fetch.message.max.bytes=10485760 - Grafana 监控（https://metricstool.pingcap.com/)
