include/master-slave.inc
Warnings:
Note	####	Sending passwords in plain text without SSL/TLS is extremely insecure.
Note	####	Storing MySQL user name or password information in the master info repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START SLAVE; see the 'START SLAVE Syntax' in the MySQL Manual for more information.
[connection master]
SET GLOBAL GTID_PURGED= "master_uuid:1-2";
CREATE TABLE t1(i INT);
DROP TABLE t1;
START SLAVE IO_THREAD;
include/wait_for_slave_io_error.inc [errno=1236]
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.''
SET GLOBAL GTID_PURGED= "master_uuid:1-2";
include/start_slave.inc
include/sync_slave_sql_with_master.inc
include/assert.inc [Slave should be able to get GTID-3 and 4 now.]
call mtr.add_suppression(".*Master has purged binary logs containing GTIDs that the slave requires.*");
include/rpl_reset.inc
CREATE TABLE t1(i INT);
DROP TABLE t1;
include/stop_slave.inc
include/rpl_restart_server.inc [server_number=1]
START SLAVE IO_THREAD;
include/wait_for_slave_io_error.inc [errno=1236]
Last_IO_Error = 'Got fatal error 1236 from master when reading data from binary log: 'Slave has more GTIDs than the master has, using the master's SERVER_UUID. This may indicate that the end of the binary log was truncated or that the last binary log file was lost, e.g., after a power or disk failure when sync_binlog != 1. The master may or may not have rolled back transactions that were already replica''
call mtr.add_suppression(".*Slave has more GTIDs than the master has.*");
SET GLOBAL GTID_PURGED= "master_uuid:1-2";
include/start_slave.inc
include/rpl_end.inc
