Debian Codegraph @

mysql-test/suite/rpl_nogtid/t/rpl_mts_relay_log_post_crash_recovery.test

raw
1 ###############################################################################
2 # Bug#21507981: REPLICATION POSITION LOST AFTER CRASH ON MTS CONFIGURED SLAVE
3 #
4 # Problem:
5 # ========
6 # Enable MTS along with crash-safe replication tables. Make sure that the
7 # server
8 # is busily inserting data with multiple threads in parallel. Shutdown mysqld
9 # uncleanly (kill -9 or power off server without notice).
10 #
11 # Now users are restarting the server with --relay-log-recovery=1 to recover
12 # the
13 # crashed slave.
14 #
15 # This results in following error:
16 # ================================
17 # 2015-06-24 13:49:03 3895 [ERROR] --relay-log-recovery cannot
18 # be executed when the slave was stopped with an error or
19 # killed in MTS mode; consider using RESET SLAVE or restart
20 # the server with --relay-log-recovery = 0 followed by
21 # START SLAVE UNTIL SQL_AFTER_MTS_GAPS.
22 #
23 # i.e relay-log-recovery will not work in MTS mode.
24 ###############################################################################
25 # Following test demonstrates that when gaps are generated due to MTS crash
26 # but not due to an error then recovery should be successful with
27 # --relay-log-recovery=1 option.
28
29 --source include/force_restart.inc
30 --source include/have_binlog_format_statement.inc
31 # Test requires master-info-repository=TABLE, relay-log-info-repository=TABLE
32 --source include/have_slave_repository_type_table.inc
33 --source include/only_mts_replica_parallel_workers.inc
34 --source include/only_mts_replica_parallel_type_database.inc
35 --source include/master-slave.inc
36
37 --let $skip_replica_start_var= FALSE
38 --source extra/rpl_tests/rpl_mts_relay_log_recovery.test
39
40 --let $skip_replica_start_var= TRUE
41 --source extra/rpl_tests/rpl_mts_relay_log_recovery.test
42
43 --source include/rpl_end.inc