-
Parveez Baig authored
There are two types of assertion failures in test. 1)In the test some operation is performed on master and on slave assertion is made whether the master_log_name and master_log_pos have got updated in mysql.slave_relay_log_info. The assertion is failng with the result that the master_log_file and position have not got synced since before the assertion is made the test doesn't guarantee whether the slave has synced it's IO_THREAD with the master. 2) some times there is assertion failure in gtid_step_assert.inc. This file checks that n number of gtid's have been added since last call to gtid_executed was made. This assertion is failing since before the assertion is made the test doesn't guaratee whether the slave's IO_THREAD is in sync with the master. Fix: Replaced assert.inc with wait_condition.inc. Added sync_slave_io_with_master wherever necessary.
Parveez Baig authoredThere are two types of assertion failures in test. 1)In the test some operation is performed on master and on slave assertion is made whether the master_log_name and master_log_pos have got updated in mysql.slave_relay_log_info. The assertion is failng with the result that the master_log_file and position have not got synced since before the assertion is made the test doesn't guarantee whether the slave has synced it's IO_THREAD with the master. 2) some times there is assertion failure in gtid_step_assert.inc. This file checks that n number of gtid's have been added since last call to gtid_executed was made. This assertion is failing since before the assertion is made the test doesn't guaratee whether the slave's IO_THREAD is in sync with the master. Fix: Replaced assert.inc with wait_condition.inc. Added sync_slave_io_with_master wherever necessary.
Loading