| 1 |
include/group_replication.inc |
| 2 |
Warnings: |
| 3 |
Note #### Sending passwords in plain text without SSL/TLS is extremely insecure. |
| 4 |
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. |
| 5 |
[connection server1] |
| 6 |
|
| 7 |
# 1. Get row from performance_schema.replication_group_member_stats |
| 8 |
# for current member. It will return one row |
| 9 |
include/assert.inc [The value of member_id should not be empty before starting group replication] |
| 10 |
|
| 11 |
# 2. Simulate bad_alloc exception for |
| 12 |
# performance_schema.replication_group_member_stats table by |
| 13 |
# enabling flow_control_simulate_bad_alloc_exception debug sync point. |
| 14 |
SET SESSION DEBUG='+d,flow_control_simulate_bad_alloc_exception'; |
| 15 |
|
| 16 |
# 3. Get row from performance_schema.replication_group_member_stats. |
| 17 |
# It will fail with ER_STD_BAD_ALLOC_ERROR error as |
| 18 |
# flow_control_simulate_bad_alloc_exception debug sync point was |
| 19 |
# activated. |
| 20 |
SELECT COUNT(*) from performance_schema.replication_group_member_stats; |
| 21 |
ERROR HY000: Memory allocation error: while getting replication_group_member_stats table rows in function get_pipeline_stats. |
| 22 |
|
| 23 |
# 4. Disable flow_control_simulate_bad_alloc_exception debug sync point. |
| 24 |
SET SESSION DEBUG='-d,flow_control_simulate_bad_alloc_exception'; |
| 25 |
|
| 26 |
# 5. Verify that member is still ONLINE |
| 27 |
include/gr_wait_for_member_state.inc |
| 28 |
|
| 29 |
# 6. Verify number of members in the group are still same |
| 30 |
include/rpl_gr_wait_for_number_of_members.inc |
| 31 |
|
| 32 |
# 7. Clean Up |
| 33 |
include/group_replication_end.inc |