mirror of
https://github.com/MariaDB/server.git
synced 2025-01-19 13:32:33 +01:00
7d1bc0a4f9
the reason for the failure is that io thread passes through a sequence of state changes before it eventually got stuck at the expect running state as NO. It's unreasonble to wait for the running status while the whole idea of the test is to get to the IO thread error. Fixed with changing the waiting condition. mysql-test/suite/rpl/r/rpl_server_id1.result: results changed mysql-test/suite/rpl/t/disabled.def: re-enabling rpl_server_id1 mysql-test/suite/rpl/t/rpl_server_id1.test: deploying the exact waiting condition i.e to wait for the slave io error.
13 lines
624 B
Text
13 lines
624 B
Text
stop slave;
|
|
drop table if exists t1,t2,t3,t4,t5,t6,t7,t8,t9;
|
|
reset master;
|
|
reset slave;
|
|
drop table if exists t1,t2,t3,t4,t5,t6,t7,t8,t9;
|
|
start slave;
|
|
reset master;
|
|
stop slave;
|
|
change master to master_port=SLAVE_PORT;
|
|
start slave;
|
|
*** must be having the replicate-same-server-id IO thread error ***
|
|
Slave_IO_Errno= 1593
|
|
Slave_IO_Error= Fatal error: The slave I/O thread stops because master and slave have equal MySQL server ids; these ids must be different for replication to work (or the --replicate-same-server-id option must be used on slave but this does not always make sense; please check the manual before using it).
|