WARN mysql_binlog_connector_rust::network::packet_channel: Stream reading binlog returns zero-length data, Expected data length: 24896, read so far: 14456

[xbitlabs]

久不久会出现下面的报错：

2025-10-10 20:27:22 WARN mysql_binlog_connector_rust::network::packet_channel: Stream reading binlog returns zero-length data, Expected data length: 24896, read so far: 14456
2025-10-10 20:27:22 WARN mysql_binlog_connector_rust::network::packet_channel: Stream reading binlog returns zero-length data, Expected data length: 24896, read so far: 14456
2025-10-10 20:27:22 WARN mysql_binlog_connector_rust::network::packet_channel: Stream reading binlog returns zero-length data, Expected data length: 24896, read so far: 14456
2025-10-10 20:27:22 WARN mysql_binlog_connector_rust::network::packet_channel: Stream reading binlog returns zero-length data, Expected data length: 24896, read so far: 14456
2025-10-10 20:27:22 WARN mysql_binlog_connector_rust::network::packet_channel: Stream reading binlog returns zero-length data, Expected data length: 24896, read so far: 14456
2025-10-10 20:27:22 WARN mysql_binlog_connector_rust::network::packet_channel: Stream reading binlog returns zero-length data, Expected data length: 24896, read so far: 14456
2025-10-10 20:27:22 WARN mysql_binlog_connector_rust::network::packet_channel: Stream reading binlog returns zero-length data, Expected data length: 24896, read so far: 14456
2025-10-10 20:27:22 WARN mysql_binlog_connector_rust::network::packet_channel: Stream reading binlog returns zero-length data, Expected data length: 24896, read so far: 14456
2025-10-10 20:27:22 WARN mysql_binlog_connector_rust::network::packet_channel: Stream reading binlog returns zero-length data, Expected data length: 24896, read so far: 14456
2025-10-10 20:27:22 WARN mysql_binlog_connector_rust::network::packet_channel: Stream reading binlog returns zero-length data, Expected data length: 24896, read so far: 14456
2025-10-10 20:27:22 WARN mysql_binlog_connector_rust::network::packet_channel: Stream reading binlog returns zero-length data, Expected data length: 24896, read so far: 14456
2025-10-10 20:27:22 WARN mysql_binlog_connector_rust::network::packet_channel: Stream reading binlog returns zero-length data, Expected data length: 24896, read so far: 14456
2025-10-10 20:27:22 WARN mysql_binlog_connector_rust::network::packet_channel: Stream reading binlog returns zero-length data, Expected data length: 24896, read so far: 14456
2025-10-10 20:27:22 WARN mysql_binlog_connector_rust::network::packet_channel: Stream reading binlog returns zero-length data, Expected data length: 24896, read so far: 14456
2025-10-10 20:27:22 WARN mysql_binlog_connector_rust::network::packet_channel: Stream reading binlog returns zero-length data, Expected data length: 24896, read so far: 14456
2025-10-10 20:27:22 WARN mysql_binlog_connector_rust::network::packet_channel: Stream reading binlog returns zero-length data, Expected data length: 24896, read so far: 14456
2025-10-10 20:27:22 WARN mysql_binlog_connector_rust::network::packet_channel: Stream reading binlog returns zero-length data, Expected data length: 24896, read so far: 14456
2025-10-10 20:27:22 WARN mysql_binlog_connector_rust::network::packet_channel: Stream reading binlog returns zero-length data, Expected data length: 24896, read so far: 14456
2025-10-10 20:27:22 WARN mysql_binlog_connector_rust::network::packet_channel: Stream reading binlog returns zero-length data, Expected data length: 24896, read so far: 14456
2025-10-10 20:27:22 WARN mysql_binlog_connector_rust::network::packet_channel: Stream reading binlog returns zero-length data, Expected data length: 24896, read so far: 14456
2025-10-10 20:27:22 WARN mysql_binlog_connector_rust::network::packet_channel: Stream reading binlog returns zero-length data, Expected data length: 24896, read so far: 14456
2025-10-10 20:27:22 WARN mysql_binlog_connector_rust::network::packet_channel: Stream reading binlog returns zero-length data, Expected data length: 24896, read so far: 14456
2025-10-10 20:27:23 WARN mysql_binlog_connector_rust::network::packet_channel: Stream reading binlog returns zero-length data, Expected data length: 24896, read so far: 14456
2025-10-10 20:27:23 WARN mysql_binlog_connector_rust::network::packet_channel: Stream reading binlog returns zero-length data, Expected data length: 24896, read so far: 14456
2025-10-10 20:27:23 ERROR send_sync: unexpected binlog data: Too many zero-length reads. Expected data length: 24896, read so far: 14456

[Zzaniu]

贴代码看看啊

[caiq1nyu]

应该是源端没写入，连接达到net_timeout阈值后被中断了，可以先在应用侧调用这个lib时增加一些重连

[caiq1nyu]

应该是源端没写入，连接达到net_timeout阈值后被中断了，可以先在应用侧调用这个lib时增加一些重连

btw, 可以检查下你开启client时是否有设置heartbeat_interval_secs：

mysql-binlog-connector-rust/src/binlog_client.rs

Line 30 in ced82d2

pub heartbeat_interval_secs: u64,

没有设置的话可以设置个比如10s，再观察下 @xbitlabs

[xbitlabs]

let mut client = BinlogClient {
    url: db_url.clone(),
    binlog_filename,
    binlog_position: binlog_position as u32,
    server_id,
    gtid_enabled,
    gtid_set,
    heartbeat_interval_secs: 30,
    timeout_secs: 60,
};

有设置心跳的

db_url=mysql://binlog_parser:123456@172...*:3306/test
server_id=200
binlog_filename=mysql-bin.005999
binlog_position=0
gtid_enabled=false
gtid_set=5a0e53c8-20be-11f0-8706-00163e18abeb:1-8,697e9d32-20bd-11f0-9bb2-00163e0a84f9:1-26,e06d73cc-6580-11ee-8c67-00163e08b525:1-11275018

@caiq1nyu

[caiq1nyu]

let mut client = BinlogClient {
    url: db_url.clone(),
    binlog_filename,
    binlog_position: binlog_position as u32,
    server_id,
    gtid_enabled,
    gtid_set,
    heartbeat_interval_secs: 30,
    timeout_secs: 60,
};

有设置心跳的

db_url=mysql://binlog_parser:123456@172...*:3306/test server_id=200 binlog_filename=mysql-bin.005999 binlog_position=0 gtid_enabled=false gtid_set=5a0e53c8-20be-11f0-8706-00163e18abeb:1-8,697e9d32-20bd-11f0-9bb2-00163e0a84f9:1-26,e06d73cc-6580-11ee-8c67-00163e08b525:1-11275018

@caiq1nyu

从配置看不出问题，可能是源端数据库的问题，比如源库压力过大暂停了binlogdump process就可能会导致你说的情况。建议复现下场景，出现大量类似：Stream reading binlog returns zero-length data, Expected data length: 24896, read so far: 14456 日志时观察源库负载，show processlist或者 SELECT * FROM performance_schema.threads WHERE PROCESSLIST_COMMAND = 'Binlog Dump' 观察binlogdump连接状态

另外不确定你用的什么版本的mysql以及什么版本的mysql-binlog-connector-rust，建议mysql-binlog-connector-rust用0.32+的版本。

[xbitlabs]

let mut client = BinlogClient {
    url: db_url.clone(),
    binlog_filename,
    binlog_position: binlog_position as u32,
    server_id,
    gtid_enabled,
    gtid_set,
    heartbeat_interval_secs: 30,
    timeout_secs: 60,
};

有设置心跳的
db_url=mysql://binlog_parser:123456@172...*:3306/test server_id=200 binlog_filename=mysql-bin.005999 binlog_position=0 gtid_enabled=false gtid_set=5a0e53c8-20be-11f0-8706-00163e18abeb:1-8,697e9d32-20bd-11f0-9bb2-00163e0a84f9:1-26,e06d73cc-6580-11ee-8c67-00163e08b525:1-11275018
@caiq1nyu

从配置看不出问题，可能是源端数据库的问题，比如源库压力过大暂停了binlogdump process就可能会导致你说的情况。建议复现下场景，出现大量类似：Stream reading binlog returns zero-length data, Expected data length: 24896, read so far: 14456 日志时观察源库负载，show processlist或者 SELECT * FROM performance_schema.threads WHERE PROCESSLIST_COMMAND = 'Binlog Dump' 观察binlogdump连接状态

另外不确定你用的什么版本的mysql以及什么版本的mysql-binlog-connector-rust，建议mysql-binlog-connector-rust用0.32+的版本。

mysql是8.0，mysql-binlog-connector-rust 0.3.2版本，可能是源库压力大，测试环境配置很垃圾
@caiq1nyu

[xbitlabs]

let mut client = BinlogClient {
    url: db_url.clone(),
    binlog_filename,
    binlog_position: binlog_position as u32,
    server_id,
    gtid_enabled,
    gtid_set,
    heartbeat_interval_secs: 30,
    timeout_secs: 60,
};

有设置心跳的
db_url=mysql://binlog_parser:123456@172...*:3306/test server_id=200 binlog_filename=mysql-bin.005999 binlog_position=0 gtid_enabled=false gtid_set=5a0e53c8-20be-11f0-8706-00163e18abeb:1-8,697e9d32-20bd-11f0-9bb2-00163e0a84f9:1-26,e06d73cc-6580-11ee-8c67-00163e08b525:1-11275018
@caiq1nyu

从配置看不出问题，可能是源端数据库的问题，比如源库压力过大暂停了binlogdump process就可能会导致你说的情况。建议复现下场景，出现大量类似：Stream reading binlog returns zero-length data, Expected data length: 24896, read so far: 14456 日志时观察源库负载，show processlist或者 SELECT * FROM performance_schema.threads WHERE PROCESSLIST_COMMAND = 'Binlog Dump' 观察binlogdump连接状态

另外不确定你用的什么版本的mysql以及什么版本的mysql-binlog-connector-rust，建议mysql-binlog-connector-rust用0.32+的版本。

mysql-binlog-connector-rust 0.3.3是修复了什么bug？
@caiq1nyu

[caiq1nyu]

let mut client = BinlogClient {
    url: db_url.clone(),
    binlog_filename,
    binlog_position: binlog_position as u32,
    server_id,
    gtid_enabled,
    gtid_set,
    heartbeat_interval_secs: 30,
    timeout_secs: 60,
};

有设置心跳的
db_url=mysql://binlog_parser:123456@172...*:3306/test server_id=200 binlog_filename=mysql-bin.005999 binlog_position=0 gtid_enabled=false gtid_set=5a0e53c8-20be-11f0-8706-00163e18abeb:1-8,697e9d32-20bd-11f0-9bb2-00163e0a84f9:1-26,e06d73cc-6580-11ee-8c67-00163e08b525:1-11275018
@caiq1nyu

从配置看不出问题，可能是源端数据库的问题，比如源库压力过大暂停了binlogdump process就可能会导致你说的情况。建议复现下场景，出现大量类似：Stream reading binlog returns zero-length data, Expected data length: 24896, read so far: 14456 日志时观察源库负载，show processlist或者 SELECT * FROM performance_schema.threads WHERE PROCESSLIST_COMMAND = 'Binlog Dump' 观察binlogdump连接状态
另外不确定你用的什么版本的mysql以及什么版本的mysql-binlog-connector-rust，建议mysql-binlog-connector-rust用0.32+的版本。

mysql是8.0，mysql-binlog-connector-rust 0.3.2版本，可能是源库压力大，测试环境配置很垃圾 @caiq1nyu

可以把timeout_secs设大一点，这样cdc crash的不会太快，源库压力过去可以续上。
032和033差别不大，033没有bugfix主要两个feature：

• feat: support keepalive setting for binlog TcpStream #33
• Table metadata parsing #30