1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
|
include/group_replication.inc
Warnings:
Note #### Sending passwords in plain text without SSL/TLS is extremely insecure.
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.
[connection server1]
############################################################
# 1. Verify that the entries corresponding to the
# instrumented memory are in the setup instruments
# table and the memory summary tables.
SELECT * FROM performance_schema.setup_instruments WHERE NAME LIKE 'memory/group_rpl/transaction_data';
NAME ENABLED TIMED PROPERTIES FLAGS VOLATILITY DOCUMENTATION
memory/group_rpl/transaction_data YES NULL global_statistics 0 Memory gets allocated for this Event name when the incoming transaction is queued to be handled by the plugin pipeline.
include/assert.inc ['There should be 1 entry corresponding to the transaction_data in the setup_instruments table after starting GR']
SELECT EVENT_NAME FROM performance_schema.memory_summary_global_by_event_name WHERE EVENT_NAME LIKE 'memory/group_rpl/transaction_data';
EVENT_NAME
memory/group_rpl/transaction_data
include/assert.inc ['There should be 1 entry corresponding to the transaction_data in the memory_summary_global_by_event_name table after starting GR']
############################################################
# 2. Verify that the sum of bytes allocated is greater than
# zero for a transaction and zero after transaction is
# finished.
CREATE TABLE t1(c1 INT PRIMARY KEY) ENGINE=innodb;
SET @@GLOBAL.DEBUG= '+d,group_replication_apply_data_packet_after_inject';
INSERT INTO t1 VALUES(1);;
[connection server_1]
SET DEBUG_SYNC= "now WAIT_FOR signal.group_replication_apply_data_packet_after_inject_reached";
include/assert.inc ['The sum of bytes allocated must be greater than 0']
SET @@GLOBAL.DEBUG= '-d,group_replication_apply_data_packet_after_inject';
SET DEBUG_SYNC= "now SIGNAL signal.group_replication_apply_data_packet_after_inject_continue";
[connection server1]
DROP TABLE t1;
############################################################
# 3. Stop GR
include/stop_group_replication.inc
##############################################################
# 4. Verify that the entries corresponding to the instrumented
# transaction_data remain in the tables after stopping GR.
SELECT * FROM performance_schema.setup_instruments WHERE NAME LIKE 'memory/group_rpl/transaction_data';
NAME ENABLED TIMED PROPERTIES FLAGS VOLATILITY DOCUMENTATION
memory/group_rpl/transaction_data YES NULL global_statistics 0 Memory gets allocated for this Event name when the incoming transaction is queued to be handled by the plugin pipeline.
include/assert.inc ['There should be 1 entry corresponding to the transaction_data in the setup_instruments table after stopping GR']
SELECT EVENT_NAME, CURRENT_NUMBER_OF_BYTES_USED FROM performance_schema.memory_summary_global_by_event_name WHERE EVENT_NAME LIKE 'memory/group_rpl/transaction_data';
EVENT_NAME CURRENT_NUMBER_OF_BYTES_USED
memory/group_rpl/transaction_data 0
include/assert.inc ['There should be 1 entry corresponding to the transaction_data in the memory_summary_global_by_event_name table after stopping GR']
#################################################################
# 5. Assert that the number of bytes allocated for
# transaction_data event must be 0.
include/assert.inc ['The sum of bytes allocated must be zero after stopping GR']
#################################################################
# 6. Cleanup
include/group_replication_end.inc
|
