-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
MDEV-19370: rpl.kill_race_condition failed in buildbot with Wrong val…
…ue for slave parameter Problem: ======= Executing test with following options will result in test failure. ./mtr rpl.kill_race_condition{,,,,,,,,,,} --repeat=10 --par 12 --mem Fix: ==== Test simulates applier thread kill scenario while applying a row event. But it doesn't wait for applier to catch the error stop. Added :wait_for_slave_sql_error.inc to catch the error. Test uses START SLAVE as a final step and doesn't wait for both threads to start. Added: start_slave.inc
- Loading branch information
Showing
2 changed files
with
18 additions
and
8 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,13 +1,16 @@ | ||
include/master-slave.inc | ||
[connection master] | ||
set global debug_dbug='d,rows_log_event_before_open_table'; | ||
set debug_sync='now WAIT_FOR before_open_table'; | ||
create table t1 (a int); | ||
set global debug_dbug='d,rows_log_event_before_open_table'; | ||
insert t1 values (1),(2),(3); | ||
set debug_sync='now WAIT_FOR before_open_table'; | ||
kill slave_sql_thread; | ||
set debug_sync='now SIGNAL go_ahead_sql'; | ||
include/wait_for_slave_sql_error.inc [errno=1927] | ||
Last_SQL_Error = Error executing row event: 'Connection was killed' | ||
set global debug_dbug=''; | ||
set debug_sync='RESET'; | ||
drop table t1; | ||
start slave; | ||
include/start_slave.inc | ||
Last_SQL_Error = | ||
include/rpl_end.inc |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters