| 1 |
############################################################################### |
| 2 |
# This test verifies that the statement replicated with group replication |
| 3 |
# will be processed by the test server telemetry component. |
| 4 |
# |
| 5 |
# 0. The test requires two servers: M1 and M2 |
| 6 |
# 1. Start group replication |
| 7 |
# 2. Install test server telemetry component on server2 |
| 8 |
# 3. Add some data on server1 |
| 9 |
# 4. Cleanup |
| 10 |
# 5. Verify telemetry component log from server2 contains replicated statement |
| 11 |
# |
| 12 |
|
| 13 |
--source include/have_server_telemetry_traces.inc |
| 14 |
--source include/have_group_replication_plugin.inc |
| 15 |
--source include/no_ps_protocol.inc |
| 16 |
|
| 17 |
--echo |
| 18 |
--echo ######################################################### |
| 19 |
--echo # 1. Start group replication |
| 20 |
|
| 21 |
--source include/group_replication.inc |
| 22 |
|
| 23 |
--echo |
| 24 |
--echo ######################################################### |
| 25 |
--echo # 2. Install test server telemetry component on server2 |
| 26 |
|
| 27 |
--let $rpl_connection_name= server2 |
| 28 |
--source include/rpl_connection.inc |
| 29 |
|
| 30 |
# Install required components. |
| 31 |
INSTALL COMPONENT 'file://component_test_server_telemetry_traces'; |
| 32 |
|
| 33 |
--echo |
| 34 |
--echo ######################################################### |
| 35 |
--echo # 3. Add some data on server1 |
| 36 |
|
| 37 |
--let $rpl_connection_name= server1 |
| 38 |
--source include/rpl_connection.inc |
| 39 |
|
| 40 |
CREATE TABLE t1 (c1 INT NOT NULL PRIMARY KEY) ENGINE=InnoDB; |
| 41 |
INSERT INTO t1 VALUES (1); |
| 42 |
INSERT INTO t1 VALUES (2); |
| 43 |
|
| 44 |
--source include/rpl_sync.inc |
| 45 |
|
| 46 |
--echo |
| 47 |
--echo ############################################################ |
| 48 |
--echo # 4. Cleanup |
| 49 |
|
| 50 |
--let $rpl_connection_name= server2 |
| 51 |
--source include/rpl_connection.inc |
| 52 |
|
| 53 |
--send UNINSTALL COMPONENT 'file://component_test_server_telemetry_traces'; |
| 54 |
|
| 55 |
--let $rpl_connection_name= server1 |
| 56 |
--source include/rpl_connection.inc |
| 57 |
|
| 58 |
DROP TABLE t1; |
| 59 |
|
| 60 |
--source include/rpl_sync.inc |
| 61 |
|
| 62 |
--let $rpl_connection_name= server2 |
| 63 |
--source include/rpl_connection.inc |
| 64 |
--sleep 0.1 |
| 65 |
--reap |
| 66 |
|
| 67 |
--source include/group_replication_end.inc |
| 68 |
|
| 69 |
--echo |
| 70 |
--echo ############################################################### |
| 71 |
--echo # 5. Verify telemetry component log from server2 contains replicated statement |
| 72 |
|
| 73 |
--let $rpl_connection_name= server2 |
| 74 |
--source include/rpl_connection.inc |
| 75 |
|
| 76 |
let $MYSQLD_DATADIR= `select @@datadir`; |
| 77 |
# To make test deterministic, do not output entire log |
| 78 |
# Just validate our statement got passed to telemetry callback |
| 79 |
# GR uses row-based replication, so we only see DDL query in the log |
| 80 |
--let $assert_text= Find replicated statement in telemetry log |
| 81 |
--let $assert_select= CREATE TABLE t1 |
| 82 |
--let $assert_file= $MYSQLD_DATADIR/test_server_telemetry_traces_component.log |
| 83 |
--let $assert_count= 2 |
| 84 |
--source include/assert_grep.inc |
| 85 |
remove_file $MYSQLD_DATADIR/test_server_telemetry_traces_component.log; |
| 86 |
|
| 87 |
|