Bug #95418 Large transactions cause "heartbeat is not compatible with local info" on slave
Submitted: 20 May 2019 4:48 Modified: 5 May 2021 15:39
Reporter: yunsheng zhu (OCA) Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: Replication Severity:S3 (Non-critical)
Version:5.6.28, 5.7.18 OS:Any
Assigned to: MySQL Verification Team CPU Architecture:Any
Tags: heartbeat, Not Compatible

File: Maximum allowed size is 50MB.
Description:
Privacy:

If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.

To split a large file:

[20 May 2019 4:49] yunsheng zhu
Mtr to repeat error "Slave I/O: Unexpected master's heartbeat data: heartbeat is  not compatible with local info"

Attachment: rpl_largetrans_unexpected_heartbeat.test (application/octet-stream, text), 10.11 KiB.