[待回复] 节点重新加入集群失败

233 1 2024-12-16 10:10

本帖最后由 lonelystar777 于 2024-12-16 12:52 编辑

有个mgr集群，其中一个节点因为硬盘空间满了而被移除了集群，现在清理了空间后，重新加入集群失败了，显示这个错误：

[Note] [MY-011735] Plugin group_replication reported: '[GCS] Error connecting using SSL 2000001 1'
[Error] [MY-011735] Plugin group_replication reported: '[GCS] Error on opening a connection to peer node 10.55.12.52:3306 when joining a group. My local port is: 33061.'
[Error] [MY-011735] Plugin group_replication reported: '[GCS] The group communication engine failed to test connectivity to the local group communication engine on 10.55.12.50:33061. This may be due to one or more invalid configuration settings. Double-check your group replication local address, firewall, SE Linux and TLS configurations and try restarting Group Replication on this server.'
[Error] [MY-011735] Plugin group_replication reported: '[GCS] The member was unable to join the group. Local port: 33061'
[Error] [MY-013780] Plugin group_replication reported: 'Failed to establish MySQL client connection in Group Replication. Error establishing connection. Please refer to the manual to make sure that you configured Group Replication properly to work with MySQL Protocol connections.'

确认没有防火墙之类的，但33061这个端口好像没有打开，以下是mgr相关配置：

loose-plugin_load_add = 'mysql_clone.so'
loose-plugin_load_add = 'group_replication.so'
loose-group_replication_group_name = "aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaa1"
loose-group_replication_local_address = 10.55.12.50:33061
loose-group_replication_group_seeds = 10.55.12.50:33061,10.55.12.51:33061,10.55.12.52:33061
loose-group_replication_start_on_boot = OFF
loose-group_replication_bootstrap_group = OFF
loose-group_replication_exit_state_action = READ_ONLY
loose-group_replication_flow_control_mode = "DISABLED"
loose-group_replication_single_primary_mode = ON
loose-group_replication_communication_max_message_size = 10M
loose-group_replication_arbitrator = 0
loose-group_replication_single_primary_fast_mode = 1
loose-group_replication_request_time_threshold = 50
loose-report_host = 10.55.12.50

MGR

全部回复(1)

只看楼主

yejr 2024-12-16 14:54:16

日志信息比较有限，不足以判断原因，请提供更多日志，包括primary和secondary节点上的日志。

初步怀疑原因：故障节点异常退出后，在原来的MGR组信息中还保留其成员节点信息，导致无法加回，需要让MGR清理掉该成员节点信息后方可重新加回，参考：https://greatsql.cn/docs/8.0.32- ... 8%E6%83%85%E5%86%B5

P.S，我们现在对GreatSQL社区用户承诺提供5*8在线免费技术支持服务，只要填个问卷就行 https://wj.qq.com/s2/11543483/9e09/ ，只需1分钟即可完成，这对我们也很重要，感谢支持