| 1 |
######################################################################## |
| 2 |
# 0. The test requires three servers: M1, M2 and M3. |
| 3 |
include/group_replication.inc [rpl_server_count=3] |
| 4 |
Warnings: |
| 5 |
Note #### Sending passwords in plain text without SSL/TLS is extremely insecure. |
| 6 |
Note #### Storing MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information. |
| 7 |
[connection server1] |
| 8 |
######################################################################## |
| 9 |
# 1. Create a basic table on all three servers. |
| 10 |
[connection server1] |
| 11 |
CREATE TABLE t1(a INT PRIMARY KEY); |
| 12 |
include/rpl_sync.inc |
| 13 |
[connection server2] |
| 14 |
SET sql_log_bin=0; |
| 15 |
call mtr.add_suppression("Fatal error during execution on the Applier process of Group Replication."); |
| 16 |
call mtr.add_suppression("The server was automatically set into read only mode after an error was detected."); |
| 17 |
call mtr.add_suppression("Skipping leave operation: concurrent attempt to leave the group is on-going."); |
| 18 |
call mtr.add_suppression("The replica coordinator and worker threads are stopped"); |
| 19 |
SET sql_log_bin=1; |
| 20 |
######################################################################## |
| 21 |
# 2. On M2: To replicate a partial transaction downloaded scenario, |
| 22 |
# setup a debug point to bring down the applier channel |
| 23 |
# if it receives a Write_rows_log_event and restart the |
| 24 |
# group replication to make the debug point effective. |
| 25 |
SET GLOBAL DEBUG="+d,stop_applier_channel_after_reading_write_rows_log_event"; |
| 26 |
include/stop_group_replication.inc |
| 27 |
include/start_group_replication.inc |
| 28 |
######################################################################## |
| 29 |
# 3. On M1: Execute an insert and wait till M2 goes offline |
| 30 |
# (because of the above debug point, applier channel will |
| 31 |
# go down after receiving Write_rows_log_event). |
| 32 |
[connection server1] |
| 33 |
INSERT INTO t1 values (12); |
| 34 |
######################################################################## |
| 35 |
# 4. On M2: Reset the debug point and restart the group replication in |
| 36 |
# order to download the transaction into the new relay log |
| 37 |
# file fully. |
| 38 |
[connection server2] |
| 39 |
SET GLOBAL DEBUG="-d,stop_applier_channel_after_reading_write_rows_log_event"; |
| 40 |
include/stop_group_replication.inc |
| 41 |
include/start_group_replication.inc |
| 42 |
include/assert.inc [Certifier broadcast thread must be running] |
| 43 |
######################################################################## |
| 44 |
# 5. On M1: Insert another tuple and do a diff tables with other nodes. |
| 45 |
# (just to check that everything is working fine). |
| 46 |
[connection server1] |
| 47 |
INSERT INTO t1 values (13); |
| 48 |
include/rpl_sync.inc |
| 49 |
include/diff_tables.inc [server1:t1, server2:t1, server3:t1] |
| 50 |
################ |
| 51 |
# 6. Cleanup. |
| 52 |
DROP TABLE t1; |
| 53 |
include/group_replication_end.inc |