MySQL多源主备同步报错:Last_IO_Error: Got fatal error 1236 from master when reading data from binary log

Last_IO_Error: Got fatal error 1236 from master when reading data from binary log: ‘The slave is connecting using CHANGE MASTER TO MASTER_AUTO_POSITION = 1, but the master has purged binary logs containing GTIDs that the slave requires.’

MySQL多源主备同步报错:Last_IO_Error: Got fatal error 1236 from master when reading data from binary log_第1张图片MySQL多源主备同步报错:Last_IO_Error: Got fatal error 1236 from master when reading data from binary log_第2张图片
在做mysql的gtid多源主备同步时start slave出现如上报错

解决报错:清除 master服务器 上的二进制日志(清除前先备份)
在这里插入图片描述
从服务器重启启动slave
MySQL多源主备同步报错:Last_IO_Error: Got fatal error 1236 from master when reading data from binary log_第3张图片

报错:Last_IO_Error: Got fatal error 1236 from master when reading data from binary log: ‘could not find next log; the first event ‘’ at 4, the last event read from ‘/var/log/mariadb/mariadb-bin.000011’ at 726, the last byte read from ‘/var/log/mariadb/mariadb-bin.000011’ at 726.’

在这里插入图片描述

解决: stop slave 后重新设置change master to …

MySQL多源主备同步报错:Last_IO_Error: Got fatal error 1236 from master when reading data from binary log_第4张图片

你可能感兴趣的:(mysql,gtid,主备同步,学习Linux踩过的坑,MySQL)