重建mgr多主集群后，3个节点的member_role均为SECONDARY
环境
数据库：社区版5.7.28
操作系统：CentOS Linux release 7.6.1810 (Core)
配置文件
no-auto-rehash
socket =/data/mysql/3306/tmp/mysql.sock # /tmp/mysql.sock
prompt ="\\u@\\h \\R:\\m:\\s> [\\d]>"
####: for global
user =mysql # mysql
basedir =/usr/local/mysql # /usr/local/mysql/
datadir =/data/mysql/3306/data # /usr/local/mysql/data
tmpdir =/data/mysql/3306/tmp
server_id =732 # 0
port =3306 # 3306
character_set_server =utf8mb4 # latin1
max_prepared_stmt_count =1048576
log_timestamps =system # utc
socket =/data/mysql/3306/tmp/mysql.sock # /tmp/mysql.sock
#
skip_name_resolve =1 # 0
auto_increment_increment =5
auto_increment_offset =3
lower_case_table_names =1 # 0
secure_file_priv =/tmp/ #null
open_files_limit =65535 # 1024
max_connections =3000
max_user_connections =800
innodb_lock_wait_timeout =20
interactive_timeout =600
wait_timeout =600
lock_wait_timeout =1800
back_log =2048
max_prepared_stmt_count =1048576
thread_stack =512K
log_error_verbosity =3
explicit_defaults_for_timestamp =1
external-locking =FALSE
thread_cache_size =256 # 9
table_open_cache =4096 # 2000
table_definition_cache =2048 # 1400
table_open_cache_instances =64 # 16
max_prepared_stmt_count =1048576 #
default_time_zone ="+8:00"
innodb_undo_directory =/data/mysql/3306/undolog
max_allowed_packet =128M
####: for binlog
log_bin_trust_function_creators =on # 0
log_bin =/data/mysql/3306/binlogs/mysql-bin #off
binlog_rows_query_log_events =on # off
log_slave_updates =on # off
expire_logs_days =7 # 0
binlog_format =row
binlog_row_image =full
binlog_cache_size =4M # 65536(64k)
binlog_checksum =none
sync_binlog =1 # 1
slave-preserve-commit-order =ON #
log_error =err.log #
general_log =off # off
general_log_file =general.log # hostname.log
####: for slow query log
slow_query_log =on # off
slow_query_log_file =/data/mysql/3306/slowlog/slow.log
log_queries_not_using_indexes =on # off
long_query_time =1.000000 # 10.000000
log_throttle_queries_not_using_indexes =60
log_slow_admin_statements =1
log_slow_slave_statements =1
####: for gtid
gtid_executed_compression_period =1000 # 1000
gtid_mode =on # off
enforce_gtid_consistency =on # off
binlog_gtid_simple_recovery =on
####: for replication
skip_slave_start =1 #
master_info_repository =table # file
relay_log_info_repository =table # file
slave_parallel_type =logical_clock # database | LOGICAL_CLOCK
slave_parallel_workers =32 # 0
rpl_semi_sync_master_enabled =1 # 0
rpl_semi_sync_slave_enabled =1 # 0
rpl_semi_sync_master_timeout =1000 # 1000(1 second)
plugin_load_add =semisync_master.so #
plugin_load_add =semisync_slave.so #
binlog_group_commit_sync_delay =500 # 0 500(0.05% seconde)
binlog_group_commit_sync_no_delay_count = 13 # 0
####: for innodb
innodb_stats_on_metadata =0
default_storage_engine =innodb # innodb
default_tmp_storage_engine =innodb # innodb
innodb_data_file_path =ibdata1:1G:autoextend # ibdata1:12M:autoextend
innodb_temp_data_file_path =ibtmp1:12M:autoextend:max:4G # ibtmp1:12M:autoextend
innodb_buffer_pool_filename =ib_buffer_pool # ib_buffer_pool
innodb_log_group_home_dir =/data/mysql/3306/binlogs/ #./
innodb_log_files_in_group =4
innodb_log_file_size =2G
innodb_file_per_table =on # on
innodb_online_alter_log_max_size =1G # 134217728(128M)
innodb_open_files =65535 # 2000
innodb_page_size =16k # 16384(16k)
innodb_thread_concurrency =8 # 0
innodb_read_io_threads =8 # 4
innodb_write_io_threads =8 # 4
innodb_purge_threads =4 # 4(garbage collection)
innodb_page_cleaners =10 # 4(flush lru list)
innodb_print_all_deadlocks =on # off
innodb_deadlock_detect =on # on
innodb_lock_wait_timeout =50 # 50
innodb_spin_wait_delay =30 #6
innodb_autoinc_lock_mode =2 # 1
innodb_io_capacity =15000 # 200
innodb_io_capacity_max =20000 # 2000
#--------Persistent Optimizer Statistics
innodb_stats_auto_recalc =on # on
innodb_stats_persistent =on # on
innodb_stats_persistent_sample_pages =64 # 20
innodb_buffer_pool_instances =18
innodb_adaptive_hash_index =on # on
innodb_change_buffering =all # all
innodb_change_buffer_max_size =25 # 25
innodb_flush_neighbors =0 # 1
innodb_doublewrite =on # on
innodb_log_buffer_size =32M # 16777216(16M)
innodb_flush_log_at_timeout =1 # 1
innodb_flush_log_at_trx_commit =1 # 1
innodb_buffer_pool_size =19200M # 134217728(128M)
autocommit =1 # 1
#--------innodb scan resistant
innodb_old_blocks_pct =37 # 37
innodb_old_blocks_time =1000 # 1000
#--------innodb read ahead
innodb_read_ahead_threshold =56 # 56 (0..64)
innodb_random_read_ahead =OFF # OFF
#--------innodb buffer pool state
innodb_buffer_pool_dump_pct =40 # 25
innodb_buffer_pool_dump_at_shutdown =ON # ON
innodb_buffer_pool_load_at_startup =ON # ON
innodb_flush_method = O_DIRECT
innodb_deadlock_detect =0
innodb_print_all_deadlocks =1
sort_buffer_size =4M
join_buffer_size =4M
innodb_status_file =1
innodb_status_output =0
innodb_status_output_locks =0
innodb_checksum_algorithm =crc32
innodb_max_dirty_pages_pct =50
innodb_lru_scan_depth =4096
read_buffer_size =8M
read_rnd_buffer_size =4M
key_buffer_size =32M
bulk_insert_buffer_size =64M
tmp_table_size =96M
max_heap_table_size =96M
myisam_sort_buffer_size =128M
myisam_max_sort_file_size =10G
myisam_repair_threads =1
min_examined_row_limit =1000
innodb_checksums =1
innodb_rollback_on_timeout =1
innodb_rollback_segments =128
innodb_sync_spin_loops =100
transaction_isolation =READ-COMMITTED
innodb_flush_sync =0
relay_log_recovery =on
max_binlog_size =1024M
max_binlog_cache_size =2G
binlog_order_commits =OFF
innodb_large_prefix =1
innodb_strict_mode =1
loose_innodb_numa_interleave =1
innodb_max_undo_log_size =4G
innodb_undo_logs =128
innodb_undo_tablespaces =95
innodb_undo_log_truncate =on
innodb_purge_rseg_truncate_frequency =128
innodb_sort_buffer_size =32M
query_cache_size =128
query_cache_type =0
internal_tmp_disk_storage_engine =innoDB
####: for mysql group replication
loose-group_replication_recovery_retry_count =10 # 10
loose-group_replication_recovery_reconnect_interval =60 # 60
loose-group_replication_allow_local_disjoint_gtids_join=off # off
loose-group_replication_allow_local_lower_version_join=off # off
loose-group_replication_ip_whitelist ="10. xxx. xxx.21,10. xxx. xxx.40,10. xxx. xxx.8"# AUTOMATIC
loose-transaction_write_set_extraction =XXHASH64 # off
loose-group_replication_group_name ="aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa" #
loose-group_replication_start_on_boot =off # off
loose-group_replication_bootstrap_group =off # off
loose-group_replication_single_primary_mode =off #
loose-group_replication_enforce_update_everywhere_checks=on #
loose-group_replication_gtid_assignment_block_size =1000000 # 1000000
loose-group_replication_poll_spin_loops =0 # 0
loose-group_replication_compression_threshold =1024 # 1000000
loose-group_replication_flow_control_mode =QUOTA # QUOTA
loose-group_replication_local_address ="10.xxx.xxx.8:33060"
loose-group_replication_group_seeds ="10.xxx.xxx.21:33060,10. xxx. xxx.40:33060,10. xxx. xxx.8:33060"
slave_rows_search_algorithms ='INDEX_SCAN,HASH_SCAN'
loose-binlog_transaction_dependency_tracking =WRITESET_SESSION
loose-transaction_write_set_extraction =XXHASH64
slave_preserve_commit_order =1
slave_net_timeout =60
log_slave_updates =on
skip_slave_start =0
max_relay_log_size =128M
relay_log =relay-bin
####for performance_schema
performance_schema =on # on
performance_schema_consumer_global_instrumentation =on # on
performance_schema_consumer_thread_instrumentation =on # on
performance_schema_consumer_events_stages_current =on # off
performance_schema_consumer_events_stages_history =on # off
performance_schema_consumer_events_stages_history_long =off # off
performance_schema_consumer_statements_digest =on # on
performance_schema_consumer_events_statements_current =on # on
performance_schema_consumer_events_statements_history =on # on
performance_schema_consumer_events_statements_history_long =off # off
performance_schema_consumer_events_waits_current =on # off
performance_schema_consumer_events_waits_history =on # off
performance_schema_consumer_events_waits_history_long =off # off
performance-schema-consumer-events-transactions-history-long =ON
performance-schema-instrument ='stage/%=ON'
performance_schema_digests_size = 40000
performance_schema_max_table_instances = 40000
performance_schema_max_sql_text_length = 4096
performance_schema_max_digest_length = 4096
#innodb monitor
innodb_monitor_enable="module_innodb"
innodb_monitor_enable="module_server"
innodb_monitor_enable="module_dml"
innodb_monitor_enable="module_ddl"
innodb_monitor_enable="module_trx"
innodb_monitor_enable="module_os"
innodb_monitor_enable="module_purge"
innodb_monitor_enable="module_log"
innodb_monitor_enable="module_lock"
innodb_monitor_enable="module_buffer"
innodb_monitor_enable="module_index"
innodb_monitor_enable="module_ibuf_system"
innodb_monitor_enable="module_buffer_page"
innodb_monitor_enable="module_adaptive_hash"
现象：mgr集群的三个节点member_role均为SECONDARY
root@localhost 10:43:06> [(none)]>SELECT MEMBER_ID, MEMBER_HOST, MEMBER_PORT, MEMBER_STATE, IF(global_status.VARIABLE_NAME IS NOT NULL, 'PRIMARY', 'SECONDARY') AS MEMBER_ROLE FROM performance_schema.replication_group_members LEFT JOIN performance_schema.global_status ON global_status.VARIABLE_NAME = 'group_replication_primary_member' AND global_status.VARIABLE_VALUE = replication_group_members.MEMBER_ID;
+--------------------------------------+-----------------+-------------+--------------+-------------+
| MEMBER_ID | MEMBER_HOST | MEMBER_PORT | MEMBER_STATE | MEMBER_ROLE |
+--------------------------------------+-----------------+-------------+--------------+-------------+
| 7f6e3726-2c21-11ee-ae25-fa163e162e50 | xxxx-bS28 | 3306 | ONLINE | SECONDARY |
| 994ec483-2c22-11ee-8470-fa163e5d1eb9 | xxxx-3V4E | 3306 | ONLINE | SECONDARY |
| dcc74dde-dd8c-11ec-8543-fa163e85107c | xxxx-yYqW | 3306 | ONLINE | SECONDARY |
+--------------------------------------+-----------------+-------------+--------------+-------------+
3 rows in set (0.00 sec)
日志（包含服务启动、重组mgr的所有日志）
引导节点（业务访问该节点）
2023-07-27T10:13:08.054418+08:00 1476400 Plugin group_replication reported: 'Group communication SSL configuration: group_replication_ssl_mode: "DISABLED"'
2023-07-27T10:13:08.054801+08:00 1476400 Plugin group_replication reported: ' Automatically adding IPv4 localhost address to the whitelist. It is mandatory that it is added.'
2023-07-27T10:13:08.054884+08:00 1476400 Plugin group_replication reported: ' SSL was not enabled'
2023-07-27T10:13:08.054905+08:00 1476400 Plugin group_replication reported: 'Initialized group communication with configuration: group_replication_group_name: "aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa"; group_replication_local_address: "10.202.149.21:33060"; group_replication_group_seeds: "10.202.149.21:33060,10.202.149.40:33060,10.202.149.8:33060"; group_replication_bootstrap_group: false; group_replication_poll_spin_loops: 0; group_replication_compression_threshold: 1024; group_replication_ip_whitelist: "10.202.149.21,10.202.149.40,10.202.149.8"'
2023-07-27T10:13:08.054933+08:00 1476400 Plugin group_replication reported: ' Configured number of attempts to join: 0'
2023-07-27T10:13:08.054939+08:00 1476400 Plugin group_replication reported: ' Configured time between attempts to join: 5 seconds'
2023-07-27T10:13:08.054970+08:00 1476400 Plugin group_replication reported: 'Member configuration: member_id: 147; member_uuid: "dcc74dde-dd8c-11ec-8543-fa163e85107c"; single-primary mode: "false"; group_replication_auto_increment_increment: 7; '
2023-07-27T10:13:08.151248+08:00 1476985 'CHANGE MASTER TO FOR CHANNEL 'group_replication_applier' executed'. Previous state master_host='<NULL>', master_port= 0, master_log_file='', master_log_pos= 70, master_bind=''. New state master_host='<NULL>', master_port= 0, master_log_file='', master_log_pos= 4, master_bind=''.
2023-07-27T10:13:08.426976+08:00 1476988 Slave SQL thread for channel 'group_replication_applier' initialized, starting replication in log 'FIRST' at position 0, relay log './relay-bin-group_replication_applier.000007' position: 4
2023-07-27T10:13:08.427057+08:00 1476400 Plugin group_replication reported: 'Group Replication applier module successfully initialized!'
2023-07-27T10:13:08.483077+08:00 0 Plugin group_replication reported: 'XCom protocol version: 3'
2023-07-27T10:13:08.483121+08:00 0 Plugin group_replication reported: 'XCom initialized and ready to accept incoming connections on port 33060'
2023-07-27T10:13:08.484233+08:00 0 Plugin group_replication reported: ' Error on opening a connection to 10.202.149.40:33060 on local port: 33060.'
2023-07-27T10:13:08.484544+08:00 0 Plugin group_replication reported: ' Error on opening a connection to 10.202.149.8:33060 on local port: 33060.'
2023-07-27T10:13:08.484820+08:00 0 Plugin group_replication reported: ' Error on opening a connection to 10.202.149.40:33060 on local port: 33060.'
2023-07-27T10:13:08.485070+08:00 0 Plugin group_replication reported: ' Error on opening a connection to 10.202.149.8:33060 on local port: 33060.'
2023-07-27T10:13:08.485281+08:00 0 Plugin group_replication reported: ' Error on opening a connection to 10.202.149.40:33060 on local port: 33060.'
2023-07-27T10:13:08.485487+08:00 0 Plugin group_replication reported: ' Error on opening a connection to 10.202.149.8:33060 on local port: 33060.'
2023-07-27T10:13:08.485759+08:00 0 Plugin group_replication reported: ' Error on opening a connection to 10.202.149.40:33060 on local port: 33060.'
2023-07-27T10:13:08.485916+08:00 0 Plugin group_replication reported: ' Error on opening a connection to 10.202.149.8:33060 on local port: 33060.'
2023-07-27T10:13:08.486112+08:00 0 Plugin group_replication reported: ' Error on opening a connection to 10.202.149.40:33060 on local port: 33060.'
2023-07-27T10:13:08.486278+08:00 0 Plugin group_replication reported: ' Error on opening a connection to 10.202.149.8:33060 on local port: 33060.'
2023-07-27T10:13:08.486547+08:00 0 Plugin group_replication reported: ' Error on opening a connection to 10.202.149.40:33060 on local port: 33060.'
2023-07-27T10:13:08.486749+08:00 0 Plugin group_replication reported: ' Error on opening a connection to 10.202.149.8:33060 on local port: 33060.'
2023-07-27T10:13:08.486969+08:00 0 Plugin group_replication reported: ' Error on opening a connection to 10.202.149.40:33060 on local port: 33060.'
2023-07-27T10:13:08.487109+08:00 0 Plugin group_replication reported: ' Error on opening a connection to 10.202.149.8:33060 on local port: 33060.'
2023-07-27T10:13:08.487276+08:00 0 Plugin group_replication reported: ' Error on opening a connection to 10.202.149.40:33060 on local port: 33060.'
2023-07-27T10:13:08.487513+08:00 0 Plugin group_replication reported: ' Error on opening a connection to 10.202.149.8:33060 on local port: 33060.'
2023-07-27T10:13:08.487750+08:00 0 Plugin group_replication reported: ' Error on opening a connection to 10.202.149.40:33060 on local port: 33060.'
2023-07-27T10:13:08.487961+08:00 0 Plugin group_replication reported: ' Error on opening a connection to 10.202.149.8:33060 on local port: 33060.'
2023-07-27T10:13:08.488237+08:00 0 Plugin group_replication reported: ' Error on opening a connection to 10.202.149.40:33060 on local port: 33060.'
2023-07-27T10:13:08.488478+08:00 0 Plugin group_replication reported: ' Error on opening a connection to 10.202.149.8:33060 on local port: 33060.'
2023-07-27T10:13:08.488500+08:00 0 Plugin group_replication reported: ' Error connecting to all peers. Member join failed. Local port: 33060'
2023-07-27T10:13:08.491072+08:00 0 Plugin group_replication reported: 'read failed'
2023-07-27T10:13:08.625397+08:00 0 Plugin group_replication reported: ' The member was unable to join the group. Local port: 33060'
2023-07-27T10:14:08.427315+08:00 1476400 Plugin group_replication reported: 'Timeout on wait for view after joining group'
2023-07-27T10:14:08.427382+08:00 1476400 Plugin group_replication reported: 'Requesting to leave the group despite of not being a member'
2023-07-27T10:14:08.427405+08:00 1476400 Plugin group_replication reported: ' The member is leaving a group without being on one.'
2023-07-27T10:14:08.553167+08:00 1476988 Error reading relay log event for channel 'group_replication_applier': slave SQL thread was killed
2023-07-27T10:14:08.554358+08:00 1476988 Slave SQL thread for channel 'group_replication_applier' exiting, replication stopped in log 'FIRST' at position 0
2023-07-27T10:14:08.614422+08:00 1476985 Plugin group_replication reported: 'The group replication applier thread was killed'
2023-07-27T10:14:09.615044+08:00 1476400 Aborted connection 1476400 to db: 'unconnected' user: 'root' host: 'localhost' (The server is not configured properly to be an active member of )
2023-07-27T10:14:09.615600+08:00 1477044 Plugin group_replication reported: 'Group communication SSL configuration: group_replication_ssl_mode: "DISABLED"'
2023-07-27T10:14:09.615754+08:00 1477044 Plugin group_replication reported: ' Automatically adding IPv4 localhost address to the whitelist. It is mandatory that it is added.'
2023-07-27T10:14:09.615813+08:00 1477044 Plugin group_replication reported: ' SSL was not enabled'
2023-07-27T10:14:09.615831+08:00 1477044 Plugin group_replication reported: 'Initialized group communication with configuration: group_replication_group_name: "aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa"; group_replication_local_address: "10.202.149.21:33060"; group_replication_group_seeds: "10.202.149.21:33060,10.202.149.40:33060,10.202.149.8:33060"; group_replication_bootstrap_group: true; group_replication_poll_spin_loops: 0; group_replication_compression_threshold: 1024; group_replication_ip_whitelist: "10.202.149.21,10.202.149.40,10.202.149.8"'
2023-07-27T10:14:09.615853+08:00 1477044 Plugin group_replication reported: ' Configured number of attempts to join: 0'
2023-07-27T10:14:09.615859+08:00 1477044 Plugin group_replication reported: ' Configured time between attempts to join: 5 seconds'
2023-07-27T10:14:09.615883+08:00 1477044 Plugin group_replication reported: 'Member configuration: member_id: 147; member_uuid: "dcc74dde-dd8c-11ec-8543-fa163e85107c"; single-primary mode: "false"; group_replication_auto_increment_increment: 7; '
2023-07-27T10:14:09.616302+08:00 1477056 'CHANGE MASTER TO FOR CHANNEL 'group_replication_applier' executed'. Previous state master_host='<NULL>', master_port= 0, master_log_file='', master_log_pos= 4, master_bind=''. New state master_host='<NULL>', master_port= 0, master_log_file='', master_log_pos= 4, master_bind=''.
2023-07-27T10:14:09.974034+08:00 1477059 Slave SQL thread for channel 'group_replication_applier' initialized, starting replication in log 'FIRST' at position 0, relay log './relay-bin-group_replication_applier.000007' position: 4
2023-07-27T10:14:09.974062+08:00 1477044 Plugin group_replication reported: 'Group Replication applier module successfully initialized!'
2023-07-27T10:14:09.974483+08:00 0 Plugin group_replication reported: 'XCom protocol version: 3'
2023-07-27T10:14:09.974514+08:00 0 Plugin group_replication reported: 'XCom initialized and ready to accept incoming connections on port 33060'
2023-07-27T10:14:10.976496+08:00 0 Plugin group_replication reported: 'Group membership changed to RightCloud-yYqW:3306 on view 16904240509758596:1.'
2023-07-27T10:14:10.976720+08:00 1477094 Plugin group_replication reported: 'Only one server alive. Declaring this server as online within thereplication group'
2023-07-27T10:14:11.280238+08:00 0 Plugin group_replication reported: 'This server was declared online within the replication group'
2023-07-27T10:15:00.405678+08:00 1476394 InnoDB: Cannot add field `BE_xid_297` in table `tmp`.`#sql_1c95_0` because after adding it, the row size is 8138 which is greater than maximum allowed size (8126) for a record on index leaf page.
2023-07-27T10:15:39.103822+08:00 0 Plugin group_replication reported: 'Members joined the group: RightCloud-3V4E:3306'
2023-07-27T10:15:39.103923+08:00 0 Plugin group_replication reported: 'Group membership changed to RightCloud-3V4E:3306, RightCloud-yYqW:3306 on view 16904240509758596:2.'
2023-07-27T10:15:39.458087+08:00 1477114 Start binlog_dump to master_thread_id(1477114) slave_server(732), pos(, 4)
2023-07-27T10:15:39.458142+08:00 1477114 Start semi-sync binlog_dump to slave (server_id: 732), pos(, 4)
2023-07-27T10:15:45.884224+08:00 0 Semi-sync replication switched ON at (mysql-bin.000359, 355308799)
2023-07-27T10:16:06.098421+08:00 0 Plugin group_replication reported: 'Members joined the group: RightCloud-bS28:3306'
2023-07-27T10:16:06.098497+08:00 0 Plugin group_replication reported: 'Group membership changed to RightCloud-bS28:3306, RightCloud-3V4E:3306,RightCloud-yYqW:3306 on view 16904240509758596:3.'
2023-07-27T10:16:06.793296+08:00 1477130 Start binlog_dump to master_thread_id(1477130) slave_server(878), pos(, 4)
2023-07-27T10:16:06.793338+08:00 1477130 Start semi-sync binlog_dump to slave (server_id: 878), pos(, 4)
2023-07-27T10:17:24.291513+08:00 1476493 InnoDB: Cannot add field `BE_xid_297` in table `tmp`.`#sql_1c95_0` because after adding it, the row size is 8138 which is greater than maximum allowed size (8126) for a record on index leaf page.
2023-07-27T10:17:24.464185+08:00 1476493 InnoDB: Cannot add field `BE_xid_297` in table `tmp`.`#sql_1c95_0` because after adding it, the row size is 8138 which is greater than maximum allowed size (8126) for a record on index leaf page.
2023-07-27T10:18:33.931105+08:00 0 /usr/local/mysql/bin/mysqld: Got an error reading communication packets
2023-07-27T10:18:34.396653+08:00 0 Plugin group_replication reported: 'The member with address RightCloud-3V4E:3306 was declared online withinthe replication group'
2023-07-27T10:18:34.976883+08:00 1477114 Semi-sync master failed on net_flush() before waiting for slave reply
2023-07-27T10:18:35.070085+08:00 1477114 Stop semi-sync binlog_dump to slave (server_id: 732)
2023-07-27T10:18:35.070159+08:00 1477114 Aborted connection 1477114 to db: 'unconnected' user: 'repl' host: '10.202.149.8' (Found net error)
2023-07-27T10:18:51.546250+08:00 0 /usr/local/mysql/bin/mysqld: Got an error reading communication packets
2023-07-27T10:18:52.118308+08:00 0 Plugin group_replication reported: 'The member with address RightCloud-bS28:3306 was declared online withinthe replication group'
2023-07-27T10:18:54.908584+08:00 1477130 Semi-sync master failed on net_flush() before waiting for slave reply
2023-07-27T10:18:54.908671+08:00 1477130 Stop semi-sync binlog_dump to slave (server_id: 878)
2023-07-27T10:18:54.908700+08:00 1477130 Aborted connection 1477130 to db: 'unconnected' user: 'repl' host: '10.202.149.40' (Found net error)
2023-07-27T10:18:55.842577+08:00 1476456 Timeout waiting for reply of binlog (file: mysql-bin.000359, pos: 355331918), semi-sync up to filemysql-bin.000359, position 355331309.
2023-07-27T10:18:55.842629+08:00 1476456 Semi-sync replication switched OFF.
添加一个节点 （注，因为备份是昨天的，添加节点后，MEMBER_STATE 处于revovering了一段时间）
2023-07-27T10:01:13.819051+08:00 0 Insecure configuration for --secure-file-priv: Location is accessible to all OS users. Consider choosinga different directory.
2023-07-27T10:01:13.819303+08:00 0 /usr/local/mysql/bin/mysqld (mysqld 5.7.28-log) starting as process 9821 ...
2023-07-27T10:01:13.896244+08:00 0 InnoDB: PUNCH HOLE support available
2023-07-27T10:01:13.896332+08:00 0 InnoDB: Mutexes and rw_locks use GCC atomic builtins
2023-07-27T10:01:13.896345+08:00 0 InnoDB: Uses event mutexes
2023-07-27T10:01:13.896351+08:00 0 InnoDB: GCC builtin __sync_synchronize() is used for memory barrier
2023-07-27T10:01:13.896356+08:00 0 InnoDB: Compressed tables use zlib 1.2.11
2023-07-27T10:01:13.896360+08:00 0 InnoDB: Using Linux native AIO
2023-07-27T10:01:13.897900+08:00 0 InnoDB: Number of pools: 1
2023-07-27T10:01:13.898088+08:00 0 InnoDB: Using CPU crc32 instructions
2023-07-27T10:01:13.904598+08:00 0 InnoDB: Initializing buffer pool, total size = 20.25G, instances = 18, chunk size = 128M
2023-07-27T10:01:13.904639+08:00 0 InnoDB: Setting NUMA memory policy to MPOL_INTERLEAVE
2023-07-27T10:01:14.994941+08:00 0 InnoDB: Setting NUMA memory policy to MPOL_DEFAULT
2023-07-27T10:01:14.994992+08:00 0 InnoDB: Completed initialization of buffer pool
2023-07-27T10:01:15.126844+08:00 0 InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2023-07-27T10:01:15.635872+08:00 0 InnoDB: Opened 95 undo tablespaces
2023-07-27T10:01:15.635908+08:00 0 InnoDB: 95 undo tablespaces made active
2023-07-27T10:01:15.636151+08:00 0 InnoDB: Highest supported file format is Barracuda.
2023-07-27T10:01:27.515300+08:00 0 InnoDB: Removed temporary tablespace data file: "ibtmp1"
2023-07-27T10:01:27.515345+08:00 0 InnoDB: Creating shared tablespace for temporary tables
2023-07-27T10:01:27.515426+08:00 0 InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2023-07-27T10:01:27.645213+08:00 0 InnoDB: File './ibtmp1' size is now 12 MB.
2023-07-27T10:01:27.646275+08:00 0 InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2023-07-27T10:01:27.646330+08:00 0 InnoDB: 32 non-redo rollback segment(s) are active.
2023-07-27T10:01:27.647214+08:00 0 InnoDB: Waiting for purge to start
2023-07-27T10:01:27.697476+08:00 0 InnoDB: page_cleaner: 1000ms intended loop took 12571ms. The settings might not be optimal. (flushed=0 and evicted=0, during the time.)
2023-07-27T10:01:27.705459+08:00 0 InnoDB: 5.7.28 started; log sequence number 383636317736
2023-07-27T10:01:27.705771+08:00 0 InnoDB: Loading buffer pool(s) from /data/mysql/3306/data/ib_buffer_pool
2023-07-27T10:01:27.706034+08:00 0 Plugin 'FEDERATED' is disabled.
2023-07-27T10:01:27.775126+08:00 0 Semi-sync replication initialized for transactions.
2023-07-27T10:01:27.775166+08:00 0 Semi-sync replication enabled on the master.
2023-07-27T10:01:27.775265+08:00 0 Starting ack receiver thread
2023-07-27T10:01:27.853561+08:00 0 Salting uuid generator variables, current_pid: 9821, server_start_time: 1690423273, bytes_sent: 0,
2023-07-27T10:01:27.853651+08:00 0 Generated uuid: '7f6e3726-2c21-11ee-ae25-fa163e162e50', server_start_time: 2764365747965785670, bytes_sent:625503232
2023-07-27T10:01:27.853675+08:00 0 No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: 7f6e3726-2c21-11ee-ae25-fa163e162e50.
2023-07-27T10:01:29.432471+08:00 0 Auto generated SSL certificates are placed in data directory.
2023-07-27T10:01:29.433269+08:00 0 CA certificate ca.pem is self signed.
2023-07-27T10:01:29.740596+08:00 0 Auto generated RSA key files are placed in data directory.
2023-07-27T10:01:29.740849+08:00 0 Server hostname (bind-address): '*'; port: 3306
2023-07-27T10:01:29.740897+08:00 0 IPv6 is available.
2023-07-27T10:01:29.740918+08:00 0 - '::' resolves to '::';
2023-07-27T10:01:29.740935+08:00 0 Server socket created on IP: '::'.
2023-07-27T10:01:30.217230+08:00 0 Relay log recovery skipped for group replication channel.
2023-07-27T10:01:30.217263+08:00 0 Recovery from master pos 70 and filefor channel 'group_replication_applier'. Previous relay log pos and relay log file had been set to 4, ./relay-bin-group_replication_applier.000007 respectively.
2023-07-27T10:01:30.247231+08:00 0 Relay log recovery skipped for group replication channel.
2023-07-27T10:01:30.247257+08:00 0 Recovery from master pos 4 and filefor channel 'group_replication_recovery'. Previous relay log pos and relay log file had been set to 4, ./relay-bin-group_replication_recovery.000006 respectively.
2023-07-27T10:01:30.251253+08:00 0 Failed to start slave threads for channel ''
2023-07-27T10:01:30.257672+08:00 0 Event Scheduler: Loaded 0 events
2023-07-27T10:01:30.258178+08:00 0 /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.7.28-log'socket: '/data/mysql/3306/tmp/mysql.sock'port: 3306MySQL Community Server (GPL)
2023-07-27T10:05:04.680378+08:00 3 @@GLOBAL.GTID_PURGED was changed from '' to 'aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa:1-52762013,
dcc74dde-dd8c-11ec-8543-fa163e85107c:1-15336730'.
2023-07-27T10:05:04.680413+08:00 3 @@GLOBAL.GTID_EXECUTED was changed from '' to 'aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa:1-52762013,
dcc74dde-dd8c-11ec-8543-fa163e85107c:1-15336730'.
2023-07-27T10:16:02.893031+08:00 3 Plugin group_replication reported: 'Group communication SSL configuration: group_replication_ssl_mode: "DISABLED"'
2023-07-27T10:16:02.893344+08:00 3 Plugin group_replication reported: ' Automatically adding IPv4 localhost address to the whitelist. It is mandatory that it is added.'
2023-07-27T10:16:02.893403+08:00 3 Plugin group_replication reported: ' SSL was not enabled'
2023-07-27T10:16:02.893420+08:00 3 Plugin group_replication reported: 'Initialized group communication with configuration: group_replication_group_name: "aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa"; group_replication_local_address: "10.202.149.40:33060"; group_replication_group_seeds: "10.202.149.21:33060,10.202.149.40:33060,10.202.149.8:33060"; group_replication_bootstrap_group: false; group_replication_poll_spin_loops: 0; group_replication_compression_threshold: 1024; group_replication_ip_whitelist: "10.202.149.21,10.202.149.40,10.202.149.8"'
2023-07-27T10:16:02.893444+08:00 3 Plugin group_replication reported: ' Configured number of attempts to join: 0'
2023-07-27T10:16:02.893450+08:00 3 Plugin group_replication reported: ' Configured time between attempts to join: 5 seconds'
2023-07-27T10:16:02.893471+08:00 3 Plugin group_replication reported: 'Member configuration: member_id: 878; member_uuid: "7f6e3726-2c21-11ee-ae25-fa163e162e50"; single-primary mode: "false"; group_replication_auto_increment_increment: 7; '
2023-07-27T10:16:02.893711+08:00 5 Plugin group_replication reported: 'Detected previous RESET MASTER invocation or an issue exists in the group replication applier relay log. Purging existing applier logs.'
2023-07-27T10:16:02.999421+08:00 5 'CHANGE MASTER TO FOR CHANNEL 'group_replication_applier' executed'. Previous state master_host='', master_port= 3306, master_log_file='', master_log_pos= 4, master_bind=''. New state master_host='<NULL>', master_port= 0, master_log_file='', master_log_pos=4, master_bind=''.
2023-07-27T10:16:03.879192+08:00 8 Slave SQL thread for channel 'group_replication_applier' initialized, starting replication in log 'FIRST' at position 0, relay log './relay-bin-group_replication_applier.000001' position: 4
2023-07-27T10:16:03.879231+08:00 3 Plugin group_replication reported: 'Group Replication applier module successfully initialized!'
2023-07-27T10:16:03.898626+08:00 0 Plugin group_replication reported: 'XCom protocol version: 3'
2023-07-27T10:16:03.898676+08:00 0 Plugin group_replication reported: 'XCom initialized and ready to accept incoming connections on port 33060'
2023-07-27T10:16:06.098796+08:00 0 Plugin group_replication reported: 'Group membership changed to RightCloud-bS28:3306, RightCloud-3V4E:3306,RightCloud-yYqW:3306 on view 16904240509758596:3.'
2023-07-27T10:16:06.098815+08:00 43 Plugin group_replication reported: 'Establishing group recovery connection with a possible donor. Attempt 1/10'
2023-07-27T10:16:06.254185+08:00 43 'CHANGE MASTER TO FOR CHANNEL 'group_replication_recovery' executed'. Previous state master_host='', master_port= 3306, master_log_file='', master_log_pos= 4, master_bind=''. New state master_host='RightCloud-yYqW', master_port= 3306, master_log_file='', master_log_pos= 4, master_bind=''.
2023-07-27T10:16:06.360214+08:00 43 Plugin group_replication reported: 'Establishing connection to a group replication recovery donor dcc74dde-dd8c-11ec-8543-fa163e85107c at RightCloud-yYqW port: 3306.'
2023-07-27T10:16:06.360595+08:00 44 Slave I/O thread: Start semi-sync replication to master 'repl@RightCloud-yYqW:3306' in log 'FIRST' at position 4
2023-07-27T10:16:06.360649+08:00 44 Storing MySQL user name or password information in the master info repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START SLAVE; see the 'START SLAVE Syntax' in the MySQL Manual for more information.
2023-07-27T10:16:06.362156+08:00 44 Slave I/O thread for channel 'group_replication_recovery': connected to master 'repl@RightCloud-yYqW:3306',replication started in log 'FIRST' at position 4
2023-07-27T10:16:06.790593+08:00 45 Slave SQL thread for channel 'group_replication_recovery' initialized, starting replication in log 'FIRST'at position 0, relay log './relay-bin-group_replication_recovery.000001' position: 4
2023-07-27T10:16:08.656698+08:00 46 Timeout waiting for reply of binlog (file: mysql-bin.000001, pos: 739), semi-sync up to file , position0.
2023-07-27T10:16:08.656733+08:00 46 Semi-sync replication switched OFF.
2023-07-27T10:18:09.039868+08:00 45 Multi-threaded slave statistics for channel 'group_replication_recovery': seconds elapsed = 123; events assigned = 63489; worker queues filled over overrun level = 0; waited due a Worker queue full = 0; waited due the total size = 0; waited at clock conflicts = 118023348100 waited (count) when Workers occupied = 0 waited when Workers occupied = 0
2023-07-27T10:18:34.396897+08:00 0 Plugin group_replication reported: 'The member with address RightCloud-3V4E:3306 was declared online withinthe replication group'
2023-07-27T10:18:51.525572+08:00 43 Plugin group_replication reported: 'Terminating existing group replication donor connection and purging the corresponding logs.'
2023-07-27T10:18:51.539904+08:00 45 Slave SQL thread for channel 'group_replication_recovery' exiting, replication stopped in log 'mysql-bin.000359' at position 355311821
2023-07-27T10:18:51.546410+08:00 44 Slave I/O thread killed while reading event for channel 'group_replication_recovery'
2023-07-27T10:18:51.546445+08:00 44 Slave I/O thread exiting for channel 'group_replication_recovery', read up to log 'mysql-bin.000359', position 355331309
2023-07-27T10:18:51.623707+08:00 43 'CHANGE MASTER TO FOR CHANNEL 'group_replication_recovery' executed'. Previous state master_host='RightCloud-yYqW', master_port= 3306, master_log_file='', master_log_pos= 4, master_bind=''. New state master_host='<NULL>', master_port= 0, master_log_file='', master_log_pos= 4, master_bind=''.
2023-07-27T10:18:52.118579+08:00 0 Plugin group_replication reported: 'This server was declared online within the replication group'
2023-07-27T10:31:46.743478+08:00 0 InnoDB: Buffer pool(s) load completed at 230727 10:31:46
2023-07-27T10:40:00.055967+08:00 8 Multi-threaded slave statistics for channel 'group_replication_applier': seconds elapsed = 1437; events assigned = 2049; worker queues filled over overrun level = 0; waited due a Worker queue full = 0; waited due the total size = 0; waited at clock conflicts = 169923500 waited (count) when Workers occupied = 0 waited when Workers occupied = 0
2023-07-27T10:52:30.513122+08:00 8 Multi-threaded slave statistics for channel 'group_replication_applier': seconds elapsed = 750; events assigned = 3073; worker queues filled over overrun level = 0; waited due a Worker queue full = 0; waited due the total size = 0; waited at clock conflicts= 343063200 waited (count) when Workers occupied = 0 waited when Workers occupied = 0
添加另一个节点
2023-07-27T10:09:14.925423+08:00 0 Insecure configuration for --secure-file-priv: Location is accessible to all OS users. Consider choosinga different directory.
2023-07-27T10:09:14.925614+08:00 0 /usr/local/mysql/bin/mysqld (mysqld 5.7.28-log) starting as process 27155 ...
2023-07-27T10:09:14.939948+08:00 0 InnoDB: PUNCH HOLE support available
2023-07-27T10:09:14.939994+08:00 0 InnoDB: Mutexes and rw_locks use GCC atomic builtins
2023-07-27T10:09:14.940001+08:00 0 InnoDB: Uses event mutexes
2023-07-27T10:09:14.940005+08:00 0 InnoDB: GCC builtin __sync_synchronize() is used for memory barrier
2023-07-27T10:09:14.940010+08:00 0 InnoDB: Compressed tables use zlib 1.2.11
2023-07-27T10:09:14.940014+08:00 0 InnoDB: Using Linux native AIO
2023-07-27T10:09:14.940977+08:00 0 InnoDB: Number of pools: 1
2023-07-27T10:09:14.941110+08:00 0 InnoDB: Using CPU crc32 instructions
2023-07-27T10:09:14.943876+08:00 0 InnoDB: Initializing buffer pool, total size = 20.25G, instances = 18, chunk size = 128M
2023-07-27T10:09:14.943904+08:00 0 InnoDB: Setting NUMA memory policy to MPOL_INTERLEAVE
2023-07-27T10:09:16.178984+08:00 0 InnoDB: Setting NUMA memory policy to MPOL_DEFAULT
2023-07-27T10:09:16.179045+08:00 0 InnoDB: Completed initialization of buffer pool
2023-07-27T10:09:16.304342+08:00 0 InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2023-07-27T10:09:16.463360+08:00 0 InnoDB: Opened 95 undo tablespaces
2023-07-27T10:09:16.463396+08:00 0 InnoDB: 95 undo tablespaces made active
2023-07-27T10:09:16.463695+08:00 0 InnoDB: Highest supported file format is Barracuda.
2023-07-27T10:09:20.614292+08:00 0 InnoDB: Removed temporary tablespace data file: "ibtmp1"
2023-07-27T10:09:20.614321+08:00 0 InnoDB: Creating shared tablespace for temporary tables
2023-07-27T10:09:20.614386+08:00 0 InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2023-07-27T10:09:20.649664+08:00 0 InnoDB: File './ibtmp1' size is now 12 MB.
2023-07-27T10:09:20.650532+08:00 0 InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2023-07-27T10:09:20.650558+08:00 0 InnoDB: 32 non-redo rollback segment(s) are active.
2023-07-27T10:09:20.651259+08:00 0 InnoDB: Waiting for purge to start
2023-07-27T10:09:20.701493+08:00 0 InnoDB: page_cleaner: 1000ms intended loop took 4397ms. The settings might not be optimal. (flushed=0 and evicted=0, during the time.)
2023-07-27T10:09:20.701723+08:00 0 InnoDB: 5.7.28 started; log sequence number 383636317736
2023-07-27T10:09:20.702060+08:00 0 InnoDB: Loading buffer pool(s) from /data/mysql/3306/data/ib_buffer_pool
2023-07-27T10:09:20.702300+08:00 0 Plugin 'FEDERATED' is disabled.
2023-07-27T10:09:20.750537+08:00 0 Semi-sync replication initialized for transactions.
2023-07-27T10:09:20.750571+08:00 0 Semi-sync replication enabled on the master.
2023-07-27T10:09:20.750657+08:00 0 Starting ack receiver thread
2023-07-27T10:09:20.764898+08:00 0 Salting uuid generator variables, current_pid: 27155, server_start_time: 1690423754, bytes_sent: 0,
2023-07-27T10:09:20.765049+08:00 0 Generated uuid: '994ec483-2c22-11ee-8470-fa163e5d1eb9', server_start_time: 7643452994268314589, bytes_sent:622902160
2023-07-27T10:09:20.765112+08:00 0 No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: 994ec483-2c22-11ee-8470-fa163e5d1eb9.
2023-07-27T10:09:21.858405+08:00 0 Auto generated SSL certificates are placed in data directory.
2023-07-27T10:09:21.859263+08:00 0 CA certificate ca.pem is self signed.
2023-07-27T10:09:22.076260+08:00 0 Auto generated RSA key files are placed in data directory.
2023-07-27T10:09:22.076524+08:00 0 Server hostname (bind-address): '*'; port: 3306
2023-07-27T10:09:22.076585+08:00 0 IPv6 is available.
2023-07-27T10:09:22.076602+08:00 0 - '::' resolves to '::';
2023-07-27T10:09:22.076626+08:00 0 Server socket created on IP: '::'.
2023-07-27T10:09:23.018481+08:00 0 Relay log recovery skipped for group replication channel.
2023-07-27T10:09:23.018506+08:00 0 Recovery from master pos 70 and filefor channel 'group_replication_applier'. Previous relay log pos and relay log file had been set to 4, ./relay-bin-group_replication_applier.000007 respectively.
2023-07-27T10:09:23.029544+08:00 0 Relay log recovery skipped for group replication channel.
2023-07-27T10:09:23.029563+08:00 0 Recovery from master pos 4 and filefor channel 'group_replication_recovery'. Previous relay log pos and relay log file had been set to 4, ./relay-bin-group_replication_recovery.000006 respectively.
2023-07-27T10:09:23.031581+08:00 0 Failed to start slave threads for channel ''
2023-07-27T10:09:24.015469+08:00 0 Event Scheduler: Loaded 0 events
2023-07-27T10:09:24.016082+08:00 0 /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.7.28-log'socket: '/data/mysql/3306/tmp/mysql.sock'port: 3306MySQL Community Server (GPL)
2023-07-27T10:11:04.104855+08:00 2 @@GLOBAL.GTID_PURGED was changed from '' to 'aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa:1-52762013,
dcc74dde-dd8c-11ec-8543-fa163e85107c:1-15336730'.
2023-07-27T10:11:04.104894+08:00 2 @@GLOBAL.GTID_EXECUTED was changed from '' to 'aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa:1-52762013,
dcc74dde-dd8c-11ec-8543-fa163e85107c:1-15336730'.
2023-07-27T10:15:34.141668+08:00 2 Plugin group_replication reported: 'Group communication SSL configuration: group_replication_ssl_mode: "DISABLED"'
2023-07-27T10:15:34.141927+08:00 2 Plugin group_replication reported: ' Automatically adding IPv4 localhost address to the whitelist. It is mandatory that it is added.'
2023-07-27T10:15:34.141985+08:00 2 Plugin group_replication reported: ' SSL was not enabled'
2023-07-27T10:15:34.142003+08:00 2 Plugin group_replication reported: 'Initialized group communication with configuration: group_replication_group_name: "aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa"; group_replication_local_address: "10.202.149.8:33060"; group_replication_group_seeds: "10.202.149.21:33060,10.202.149.40:33060,10.202.149.8:33060"; group_replication_bootstrap_group: false; group_replication_poll_spin_loops: 0; group_replication_compression_threshold: 1024; group_replication_ip_whitelist: "10.202.149.21,10.202.149.40,10.202.149.8"'
2023-07-27T10:15:34.142031+08:00 2 Plugin group_replication reported: ' Configured number of attempts to join: 0'
2023-07-27T10:15:34.142039+08:00 2 Plugin group_replication reported: ' Configured time between attempts to join: 5 seconds'
2023-07-27T10:15:34.142059+08:00 2 Plugin group_replication reported: 'Member configuration: member_id: 732; member_uuid: "994ec483-2c22-11ee-8470-fa163e5d1eb9"; single-primary mode: "false"; group_replication_auto_increment_increment: 7; '
2023-07-27T10:15:34.142214+08:00 4 Plugin group_replication reported: 'Detected previous RESET MASTER invocation or an issue exists in the group replication applier relay log. Purging existing applier logs.'
2023-07-27T10:15:34.188954+08:00 4 'CHANGE MASTER TO FOR CHANNEL 'group_replication_applier' executed'. Previous state master_host='', master_port= 3306, master_log_file='', master_log_pos= 4, master_bind=''. New state master_host='<NULL>', master_port= 0, master_log_file='', master_log_pos=4, master_bind=''.
2023-07-27T10:15:34.352600+08:00 7 Slave SQL thread for channel 'group_replication_applier' initialized, starting replication in log 'FIRST' at position 0, relay log './relay-bin-group_replication_applier.000001' position: 4
2023-07-27T10:15:34.352637+08:00 2 Plugin group_replication reported: 'Group Replication applier module successfully initialized!'
2023-07-27T10:15:34.369351+08:00 0 Plugin group_replication reported: 'XCom protocol version: 3'
2023-07-27T10:15:34.369412+08:00 0 Plugin group_replication reported: 'XCom initialized and ready to accept incoming connections on port 33060'
2023-07-27T10:15:39.103851+08:00 42 Plugin group_replication reported: 'Establishing group recovery connection with a possible donor. Attempt 1/10'
2023-07-27T10:15:39.103932+08:00 0 Plugin group_replication reported: 'Group membership changed to RightCloud-3V4E:3306, RightCloud-yYqW:3306 on view 16904240509758596:2.'
2023-07-27T10:15:39.140053+08:00 42 'CHANGE MASTER TO FOR CHANNEL 'group_replication_recovery' executed'. Previous state master_host='', master_port= 3306, master_log_file='', master_log_pos= 4, master_bind=''. New state master_host='RightCloud-yYqW', master_port= 3306, master_log_file='', master_log_pos= 4, master_bind=''.
2023-07-27T10:15:39.175518+08:00 42 Plugin group_replication reported: 'Establishing connection to a group replication recovery donor dcc74dde-dd8c-11ec-8543-fa163e85107c at RightCloud-yYqW port: 3306.'
2023-07-27T10:15:39.175896+08:00 43 Slave I/O thread: Start semi-sync replication to master 'repl@RightCloud-yYqW:3306' in log 'FIRST' at position 4
2023-07-27T10:15:39.175948+08:00 43 Storing MySQL user name or password information in the master info repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START SLAVE; see the 'START SLAVE Syntax' in the MySQL Manual for more information.
2023-07-27T10:15:39.177163+08:00 43 Slave I/O thread for channel 'group_replication_recovery': connected to master 'repl@RightCloud-yYqW:3306',replication started in log 'FIRST' at position 4
2023-07-27T10:15:39.342726+08:00 44 Slave SQL thread for channel 'group_replication_recovery' initialized, starting replication in log 'FIRST'at position 0, relay log './relay-bin-group_replication_recovery.000001' position: 4
2023-07-27T10:15:46.329748+08:00 45 Timeout waiting for reply of binlog (file: mysql-bin.000001, pos: 739), semi-sync up to file , position0.
2023-07-27T10:15:46.329797+08:00 45 Semi-sync replication switched OFF.
2023-07-27T10:16:06.097503+08:00 0 Plugin group_replication reported: 'Members joined the group: RightCloud-bS28:3306'
2023-07-27T10:16:06.097577+08:00 0 Plugin group_replication reported: 'Group membership changed to RightCloud-bS28:3306, RightCloud-3V4E:3306,RightCloud-yYqW:3306 on view 16904240509758596:3.'
2023-07-27T10:17:40.587343+08:00 44 Multi-threaded slave statistics for channel 'group_replication_recovery': seconds elapsed = 121; events assigned = 57345; worker queues filled over overrun level = 0; waited due a Worker queue full = 0; waited due the total size = 0; waited at clock conflicts = 112315460600 waited (count) when Workers occupied = 0 waited when Workers occupied = 0
2023-07-27T10:18:33.924137+08:00 42 Plugin group_replication reported: 'Terminating existing group replication donor connection and purging the corresponding logs.'
2023-07-27T10:18:33.928467+08:00 44 Slave SQL thread for channel 'group_replication_recovery' exiting, replication stopped in log 'mysql-bin.000359' at position 355307581
2023-07-27T10:18:33.930342+08:00 43 Slave I/O thread killed while reading event for channel 'group_replication_recovery'
2023-07-27T10:18:33.930371+08:00 43 Slave I/O thread exiting for channel 'group_replication_recovery', read up to log 'mysql-bin.000359', position 355328873
2023-07-27T10:18:33.967526+08:00 42 'CHANGE MASTER TO FOR CHANNEL 'group_replication_recovery' executed'. Previous state master_host='RightCloud-yYqW', master_port= 3306, master_log_file='', master_log_pos= 4, master_bind=''. New state master_host='<NULL>', master_port= 0, master_log_file='', master_log_pos= 4, master_bind=''.
2023-07-27T10:18:34.396061+08:00 0 Plugin group_replication reported: 'This server was declared online within the replication group'
2023-07-27T10:18:40.775121+08:00 0 InnoDB: page_cleaner: 1000ms intended loop took 4022ms. The settings might not be optimal. (flushed=4598 and evicted=0, during the time.)
2023-07-27T10:18:52.117676+08:00 0 Plugin group_replication reported: 'The member with address RightCloud-bS28:3306 was declared online withinthe replication group'
2023-07-27T10:25:53.184950+08:00 2 Aborted connection 2 to db: 'unconnected' user: 'root' host: 'localhost' (Got timeout reading communicationpackets)
2023-07-27T10:28:04.989347+08:00 7 Multi-threaded slave statistics for channel 'group_replication_applier': seconds elapsed = 750; events assigned = 1025; worker queues filled over overrun level = 0; waited due a Worker queue full = 0; waited due the total size = 0; waited at clock conflicts= 89501900 waited (count) when Workers occupied = 0 waited when Workers occupied = 0
2023-07-27T10:37:11.132928+08:00 0 InnoDB: Buffer pool(s) load completed at 230727 10:37:11
2023-07-27T10:39:45.028556+08:00 7 Multi-threaded slave statistics for channel 'group_replication_applier': seconds elapsed = 701; events assigned = 2049; worker queues filled over overrun level = 0; waited due a Worker queue full = 0; waited due the total size = 0; waited at clock conflicts= 115819900 waited (count) when Workers occupied = 0 waited when Workers occupied = 0
2023-07-27T10:51:50.505914+08:00 7 Multi-threaded slave statistics for channel 'group_replication_applier': seconds elapsed = 725; events assigned = 3073; worker queues filled over overrun level = 0; waited due a Worker queue full = 0; waited due the total size = 0; waited at clock conflicts= 325558800 waited (count) when Workers occupied = 0 waited when Workers occupied = 0
2023-07-27T11:02:11.316781+08:00 7 Multi-threaded slave statistics for channel 'group_replication_applier': seconds elapsed = 621; events assigned = 4097; worker queues filled over overrun level = 0; waited due a Worker queue full = 0; waited due the total size = 0; waited at clock conflicts= 558361900 waited (count) when Workers occupied = 0 waited when Workers occupied = 0
除此之外，在应用连接的节点，日志中存在以下warning，不知道有没有影响
2023-07-27T10:19:31.060702+08:00 1476493 InnoDB: Cannot add field `BE_xid_297` in table `tmp`.`#sql_1c95_0` because after adding it, the row size is 8138 which is greater than maximum allowed size (8126) for a record on index leaf page.
2023-07-27T10:19:31.233379+08:00 1476493 InnoDB: Cannot add field `BE_xid_297` in table `tmp`.`#sql_1c95_0` because after adding it, the row size is 8138 which is greater than maximum allowed size (8126) for a record on index leaf page.
2023-07-27T10:20:00.534484+08:00 1476493 InnoDB: Cannot add field `BE_xid_297` in table `tmp`.`#sql_1c95_0` because after adding it, the row size is 8138 which is greater than maximum allowed size (8126) for a record on index leaf page.
2023-07-27T10:20:04.176481+08:00 1476494 InnoDB: Cannot add field `BE_xid_297` in table `tmp`.`#sql_1c95_0` because after adding it, the row size is 8138 which is greater than maximum allowed size (8126) for a record on index leaf page.
2023-07-27T10:20:04.413869+08:00 1476494 InnoDB: Cannot add field `BE_xid_297` in table `tmp`.`#sql_1c95_0` because after adding it, the row size is 8138 which is greater than maximum allowed size (8126) for a record on index leaf page.
2023-07-27T10:20:54.409015+08:00 1476494 InnoDB: Cannot add field `BE_xid_297` in table `tmp`.`#sql_1c95_0` because after adding it, the row size is 8138 which is greater than maximum allowed size (8126) for a record on index leaf page.
2023-07-27T10:20:54.593275+08:00 1476494 InnoDB: Cannot add field `BE_xid_297` in table `tmp`.`#sql_1c95_0` because after adding it, the row size is 8138 which is greater than maximum allowed size (8126) for a record on index leaf page.
2023-07-27T10:21:23.036991+08:00 1476542 InnoDB: Cannot add field `BE_xid_297` in table `tmp`.`#sql_1c95_0` because after adding it, the row size is 8138 which is greater than maximum allowed size (8126) for a record on index leaf page.
2023-07-27T10:21:23.212127+08:00 1476542 InnoDB: Cannot add field `BE_xid_297` in table `tmp`.`#sql_1c95_0` because after adding it, the row size is 8138 which is greater than maximum allowed size (8126) for a record on index leaf page.
2023-07-27T10:21:25.768210+08:00 1476542 InnoDB: Cannot add field `BE_xid_297` in table `tmp`.`#sql_1c95_0` because after adding it, the row size is 8138 which is greater than maximum allowed size (8126) for a record on index leaf page.
2023-07-27T10:21:25.929433+08:00 1476542 InnoDB: Cannot add field `BE_xid_297` in table `tmp`.`#sql_1c95_0` because after adding it, the row size is 8138 which is greater than maximum allowed size (8126) for a record on index leaf page.
2023-07-27T10:21:46.722477+08:00 1476542 InnoDB: Cannot add field `BE_xid_297` in table `tmp`.`#sql_1c95_0` because after adding it, the row size is 8138 which is greater than maximum allowed size (8126) for a record on index leaf page.
2023-07-27T10:21:46.949259+08:00 1476542 InnoDB: Cannot add field `BE_xid_297` in table `tmp`.`#sql_1c95_0` because after adding it, the row size is 8138 which is greater than maximum allowed size (8126) for a record on index leaf page.
2023-07-27T10:25:00.602690+08:00 1476576 InnoDB: Cannot add field `BE_xid_297` in table `tmp`.`#sql_1c95_0` because after adding it, the row size is 8138 which is greater than maximum allowed size (8126) for a record on index leaf page.
2023-07-27T10:26:59.835599+08:00 1476741 InnoDB: Cannot add field `BE_xid_297` in table `tmp`.`#sql_1c95_0` because after adding it, the row size is 8138 which is greater than maximum allowed size (8126) for a record on index leaf page.
2023-07-27T10:26:59.999562+08:00 1476741 InnoDB: Cannot add field `BE_xid_297` in table `tmp`.`#sql_1c95_0` because after adding it, the row size is 8138 which is greater than maximum allowed size (8126) for a record on index leaf page.
2023-07-27T10:27:56.545560+08:00 1476674 InnoDB: Cannot add field `BE_xid_297` in table `tmp`.`#sql_1c95_0` because after adding it, the row size is 8138 which is greater than maximum allowed size (8126) for a record on index leaf page.
2023-07-27T10:27:58.062483+08:00 1476674 InnoDB: Cannot add field `BE_xid_297` in table `tmp`.`#sql_1c95_0` because after adding it, the row size is 8138 which is greater than maximum allowed size (8126) for a record on index leaf page.
2023-07-27T10:28:05.023979+08:00 1476674 InnoDB: Cannot add field `BE_xid_297` in table `tmp`.`#sql_1c95_0` because after adding it, the row size is 8138 which is greater than maximum allowed size (8126) for a record on index leaf page.
2023-07-27T10:28:06.398972+08:00 1476674 InnoDB: Cannot add field `BE_xid_297` in table `tmp`.`#sql_1c95_0` because after adding it, the row size is 8138 which is greater than maximum allowed size (8126) for a record on index leaf page.
2023-07-27T10:28:50.790333+08:00 1476741 InnoDB: Cannot add field `BE_xid_297` in table `tmp`.`#sql_1c95_0` because after adding it, the row size is 8138 which is greater than maximum allowed size (8126) for a record on index leaf page.
2023-07-27T10:28:52.204412+08:00 1476741 InnoDB: Cannot add field `BE_xid_297` in table `tmp`.`#sql_1c95_0` because after adding it, the row size is 8138 which is greater than maximum allowed size (8126) for a record on index leaf page.
2023-07-27T10:28:54.230095+08:00 1476741 InnoDB: Cannot add field `BE_xid_297` in table `tmp`.`#sql_1c95_0` because after adding it, the row size is 8138 which is greater than maximum allowed size (8126) for a record on index leaf page.
2023-07-27T10:28:54.371526+08:00 1476741 InnoDB: Cannot add field `BE_xid_297` in table `tmp`.`#sql_1c95_0` because after adding it, the row size is 8138 which is greater than maximum allowed size (8126) for a record on index leaf page.
2023-07-27T10:29:15.777888+08:00 1476741 InnoDB: Cannot add field `BE_xid_297` in table `tmp`.`#sql_1c95_0` because after adding it, the row size is 8138 which is greater than maximum allowed size (8126) for a record on index leaf page.
2023-07-27T10:29:17.123113+08:00 1476741 InnoDB: Cannot add field `BE_xid_297` in table `tmp`.`#sql_1c95_0` because after adding it, the row size is 8138 which is greater than maximum allowed size (8126) for a record on index leaf page.
2023-07-27T10:29:21.624351+08:00 1476789 InnoDB: Cannot add field `BE_xid_297` in table `tmp`.`#sql_1c95_0` because after adding it, the row size is 8138 which is greater than maximum allowed size (8126) for a record on index leaf page.
2023-07-27T10:29:23.092074+08:00 1476789 InnoDB: Cannot add field `BE_xid_297` in table `tmp`.`#sql_1c95_0` because after adding it, the row size is 8138 which is greater than maximum allowed size (8126) for a record on index leaf page.
2023-07-27T10:30:00.568285+08:00 1476741 InnoDB: Cannot add field `BE_xid_297` in table `tmp`.`#sql_1c95_0` because after adding it, the row size is 8138 which is greater than maximum allowed size (8126) for a record on index leaf page.
2023-07-27T10:35:00.657030+08:00 1476880 InnoDB: Cannot add field `BE_xid_297` in table `tmp`.`#sql_1c95_0` because after adding it, the row size is 8138 which is greater than maximum allowed size (8126) for a record on index leaf page.
2023-07-27T10:40:00.469610+08:00 1477143 InnoDB: Cannot add field `BE_xid_297` in table `tmp`.`#sql_1c95_0` because after adding it, the row size is 8138 which is greater than maximum allowed size (8126) for a record on index leaf page.
2023-07-27T10:45:00.513200+08:00 1477155 InnoDB: Cannot add field `BE_xid_297` in table `tmp`.`#sql_1c95_0` because after adding it, the row size is 8138 which is greater than maximum allowed size (8126) for a record on index leaf page.
2023-07-27T10:50:00.685567+08:00 1477246 InnoDB: Cannot add field `BE_xid_297` in table `tmp`.`#sql_1c95_0` because after adding it, the row size is 8138 which is greater than maximum allowed size (8126) for a record on index leaf page.
2023-07-27T10:50:44.313512+08:00 1477246 InnoDB: Cannot add field `BE_xid_297` in table `tmp`.`#sql_1c95_0` because after adding it, the row size is 8138 which is greater than maximum allowed size (8126) for a record on index leaf page.
2023-07-27T10:50:44.471090+08:00 1477246 InnoDB: Cannot add field `BE_xid_297` in table `tmp`.`#sql_1c95_0` because after adding it, the row size is 8138 which is greater than maximum allowed size (8126) for a record on index leaf page.
2023-07-27T10:50:52.186654+08:00 1477246 InnoDB: Cannot add field `BE_xid_297` in table `tmp`.`#sql_1c95_0` because after adding it, the row size is 8138 which is greater than maximum allowed size (8126) for a record on index leaf page.
2023-07-27T10:50:52.382422+08:00 1477246 InnoDB: Cannot add field `BE_xid_297` in table `tmp`.`#sql_1c95_0` because after adding it, the row size is 8138 which is greater than maximum allowed size (8126) for a record on index leaf page.
2023-07-27T10:55:00.657477+08:00 1477327 InnoDB: Cannot add field `BE_xid_297` in table `tmp`.`#sql_1c95_0` because after adding it, the row size is 8138 which is greater than maximum allowed size (8126) for a record on index leaf page.
2023-07-27T11:00:00.647925+08:00 1477492 InnoDB: Cannot add field `BE_xid_297` in table `tmp`.`#sql_1c95_0` because after adding it, the row size is 8138 which is greater than maximum allowed size (8126) for a record on index leaf page.
2023-07-27T11:05:00.743175+08:00 1477590 InnoDB: Cannot add field `BE_xid_297` in table `tmp`.`#sql_1c95_0` because after adding it, the row size is 8138 which is greater than maximum allowed size (8126) for a record on index leaf page.
2023-07-27T11:09:02.833695+08:00 1477789 InnoDB: Cannot add field `BE_xid_297` in table `tmp`.`#sql_1c95_0` because after adding it, the row size is 8138 which is greater than maximum allowed size (8126) for a record on index leaf page.
2023-07-27T11:09:03.122306+08:00 1477789 InnoDB: Cannot add field `BE_xid_297` in table `tmp`.`#sql_1c95_0` because after adding it, the row size is 8138 which is greater than maximum allowed size (8126) for a record on index leaf page.
2023-07-27T11:10:00.558656+08:00 1477788 InnoDB: Cannot add field `BE_xid_297` in table `tmp`.`#sql_1c95_0` because after adding it, the row size is 8138 which is greater than maximum allowed size (8126) for a record on index leaf page.
2023-07-27T11:10:19.341661+08:00 1477883 InnoDB: Cannot add field `BE_xid_297` in table `tmp`.`#sql_1c95_0` because after adding it, the row size is 8138 which is greater than maximum allowed size (8126) for a record on index leaf page.
2023-07-27T11:10:19.507152+08:00 1477883 InnoDB: Cannot add field `BE_xid_297` in table `tmp`.`#sql_1c95_0` because after adding it, the row size is 8138 which is greater than maximum allowed size (8126) for a record on index leaf page.
2023-07-27T11:10:47.610140+08:00 1477883 InnoDB: Cannot add field `BE_xid_297` in table `tmp`.`#sql_1c95_0` because after adding it, the row size is 8138 which is greater than maximum allowed size (8126) for a record on index leaf page.
2023-07-27T11:10:47.771578+08:00 1477883 InnoDB: Cannot add field `BE_xid_297` in table `tmp`.`#sql_1c95_0` because after adding it, the row size is 8138 which is greater than maximum allowed size (8126) for a record on index leaf page.
2023-07-27T11:12:37.955320+08:00 0 InnoDB: page_cleaner: 1000ms intended loop took 13878ms. The settings might not be optimal. (flushed=10 andevicted=0, during the time.)
2023-07-27T11:12:57.932366+08:00 0 InnoDB: page_cleaner: 1000ms intended loop took 14103ms. The settings might not be optimal. (flushed=13 andevicted=0, during the time.)
2023-07-27T11:13:10.381767+08:00 0 InnoDB: page_cleaner: 1000ms intended loop took 6448ms. The settings might not be optimal. (flushed=74 and evicted=0, during the time.)
连接使用的MySQL客户端版本号是多少？
$ mysql --version 看看 yejr 发表于 2023-7-27 11:29
连接使用的MySQL客户端版本号是多少？
$ mysql --version 看看
# mysql -V
mysqlVer 14.14 Distrib 5.7.28, for linux-glibc2.12 (x86_64) usingEditLine wrapper 金同学 发表于 2023-7-27 11:31
# mysql -V
mysqlVer 14.14 Distrib 5.7.28, for linux-glibc2.12 (x86_64) u ...
应该不对，怀疑你是用了8.0的客户端连接的，所以才有MEMBER_ROLE这列
因为在5.7版本中，是没有MEMBER_ROLE这列的（只有在GreatSQL 5.7.36-39版本中才支持）
你再仔细检查检查 yejr 发表于 2023-7-27 11:53
应该不对，怀疑你是用了8.0的客户端连接的，所以才有MEMBER_ROLE这列
因为在5.7版本中，是没有MEMBER_ROL ...
SELECT
MEMBER_ID,
MEMBER_HOST,
MEMBER_PORT,
MEMBER_STATE,
IF(global_status.VARIABLE_NAME IS NOT NULL,
'PRIMARY',
'SECONDARY') AS MEMBER_ROLE
FROM
performance_schema.replication_group_members
LEFT JOIN
performance_schema.global_status ON global_status.VARIABLE_NAME = 'group_replication_primary_member'
AND global_status.VARIABLE_VALUE = replication_group_members.MEMBER_ID;
yejr 发表于 2023-7-27 11:53
应该不对，怀疑你是用了8.0的客户端连接的，所以才有MEMBER_ROLE这列
因为在5.7版本中，是没有MEMBER_ROL ...
我是关联查询出来的，可能跟我的SQL有关。 yejr 发表于 2023-7-27 11:53
应该不对，怀疑你是用了8.0的客户端连接的，所以才有MEMBER_ROLE这列
因为在5.7版本中，是没有MEMBER_ROL ...
感谢老师解答。 金同学 发表于 2023-7-27 14:11
感谢老师解答。
该查询SQL确实不严谨：
group_replication_primary_member
Shows the primary member's UUID when the group is operating in single-primary mode. If the group is operating in multi-primary mode, shows an empty string.
详见：https://dev.mysql.com/doc/refman/5.7/en/server-status-variables.html#statvar_group_replication_primary_member
页:
[1]