Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.0.1, 5.5.29
-
None
-
None
Description
Test rpl.rpl_rotate_purge_deadlock has in the beginning:
source include/master-slave.inc;
|
source include/have_debug_sync.inc;
|
source include/have_binlog_format_row.inc;
|
source include/have_innodb.inc;
|
It means that when debug_sync is not enabled, or binlog format is not 'row', or there's no innodb master-slave configuration will be already set up and won't be torn down. So any subsequent test involving master-slave configuration will break because it won't be able to set it up.
I guess just making master-slave.inc the last in this list is enough to fix the problem.
Hi Pavel,
Have you ever seen an actual failure due to the described problem with rpl.rpl_rotate_purge_deadlock?
I'm wondering because while generally you are right about the wrong order, in practice I think nothing wrong should ever happen since the test in question has its own config file, so the servers should be restarted after it anyway. So if you did see a failure, maybe we should look deeper into MTR logic.