Fix sporadic failure of test rpl.rpl_gtid_startpos
The test did RESET MASTER and then tried to use --sync_with_master to wait for GTID-based replication to catch up. This though has a race, there is a small window where the _old_ pre-RESET MASTER position on the slave is higher than the new pos-RESET MASTER position, causing the --sync_with_master to be a no-op. Fix by using include/wait_condition.inc instead.
Showing
Please register or sign in to comment