MySQL 组复制 : Timeout while waiting for the group communication engine to be ready-6ren

MySQL 组复制 : Timeout while waiting for the group communication engine to be ready

转载作者：行者123 更新时间：2023-11-29 02:11:56

我在将第二个实例加入 MySQL 复制组时遇到问题。它似乎是通信错误或超时错误。简而言之，我在第二个节点的日志中看到了这个错误:

"Timeout while waiting for the group communication engine to be ready!"
"The group communication engine is not ready for the member to join. Local port: 33061"

我建群的步骤:

1) 首先，我确保在两台服务器之间打开了正确的端口:

作为引用，我使用这四个变量来保护隐私:

AA.AAA.AA.A = 我的第一个服务器的公共(public) IP 地址
AA.0.0.000 = 我的第一个服务器的私有(private) IP 地址
BBB.BBB.BBB.BBB = 我的第二台服务器的公共(public) IP 地址
BBB.0.0.000 = 我的第二台服务器的私有(private) IP 地址

第一台服务器位于亚马逊 AWS 上，它有一个安全组，在 3306 和 33061 上向 BBB.BBB.BBB.BBB 开放。

第二个服务器位于私有(private)服务器上，它有一个防火墙，允许来自 3306 和 33061 上的 AA.AAA.AA.A 的流量。

从第一个服务器，确保我可以访问第二个服务器:

mysql -u repl -p'XXXXXXXXXXXXX' -h BBB.BBB.BBB.BBB
telnet BBB.BBB.BBB.BBB 3306
telnet BBB.BBB.BBB.BBB 33061
telnet BBB.BBB.BBB.BBB 7777 #Times out, as expected

从第一个服务器，确保我可以建立传出连接:

curl portquiz.net:3306
curl portquiz.net:33061

从第二台服务器，确保我可以访问第二台服务器:

mysql -u repl -p'XXXXXXXXXXXXX' -h AA.AAA.AA.A
telnet AA.AAA.AA.A 3306
telnet AA.AAA.AA.A 33061
telnet AA.AAA.AA.A 7777 #Times out, as expected

从第二台服务器，确保我可以建立传出连接:

curl portquiz.net:3306
curl portquiz.net:33061

这一切似乎都在正常工作!

2) 接下来，我使用以下配置在每台服务器上启动 MySQL:

我的第一台服务器的配置文件:

[mysqld_safe]
nice                                    = 0
socket                                  = /var/run/mysqld/mysqld.sock

[mysqld]
basedir                                 = /usr
bind_address                            = 0.0.0.0
binlog_checksum                         = NONE
binlog_format                           = ROW
datadir                                 = /var/lib/mysql
enforce_gtid_consistency                = ON
general_log                             = 1
general_log_file                        = /var/log/mysql/mysql.log
gtid_mode                               = ON
key_buffer_size                         = 8388608
lc_messages_dir                         = /usr/share/mysql
log_bin                                 = binlog
log_error                               = /var/log/mysql/error.log
log_slave_updates                       = ON
long_query_time                         = 60
loose-group_replication_allow_local_disjoint_gtids_join= ON
loose-group_replication_bootstrap_group = OFF
loose-group_replication_enforce_update_everywhere_checks= ON
loose-group_replication_group_name      = ZZZZZZ-ZZZZZZ-ZZZZZZ-ZZZZZZ
loose-group_replication_group_seeds     = AA.0.0.000:33061,BBB.BBB.BBB.BBB:33061
loose-group_replication_ip_whitelist    = AA.0.0.000,BBB.BBB.BBB.BBB,BBB.0.0.000
loose-group_replication_local_address   = AA.0.0.000:33061
loose-group_replication_recovery_use_ssl= 1
loose-group_replication_single_primary_mode= OFF
loose-group_replication_ssl_mode        = REQUIRED
loose-group_replication_start_on_boot   = OFF
master_info_repository                  = TABLE
max_allowed_packet                      = 16M
max_binlog_size                         = 100M
max_connect_errors                      = 100000000
pid-file                                = /var/run/mysqld/mysqld.pid
port                                    = 3306
relay_log                               = first-server-relay-bin
relay_log_info_repository               = TABLE
report_host                             = AA.AAA.AA.A
server_id                               = 1
skip_external_locking
slow_query_log                          = 1
slow_query_log_file                     = /var/log/mysql/slow_query.log
socket                                  = /var/run/mysqld/mysqld.sock
thread_cache_size                       = 8
thread_stack                            = 192K
tmpdir                                  = /tmp
transaction_write_set_extraction        = XXHASH64
user                                    = mysql

[mysqldump]
max_allowed_packet                      = 16M
quick
quote_names

[mysql]
no_auto_rehash

[isamchk]
key_buffer_size                         = 16M

[client]
port                                    = 3306
socket                                  = /var/run/mysqld/mysqld.sock

!includedir /etc/mysql/conf.d/

这是我的第二个服务器的配置:

[mysqld_safe]
nice                                    = 0
socket                                  = /var/run/mysqld/mysqld.sock

[mysqld]
basedir                                 = /usr
bind_address                            = 0.0.0.0
binlog_checksum                         = NONE
binlog_format                           = ROW
datadir                                 = /var/lib/mysql
enforce_gtid_consistency                = ON
general_log                             = 1
general_log_file                        = /var/log/mysql/mysql.log
gtid_mode                               = ON
key_buffer_size                         = 8388608
lc_messages_dir                         = /usr/share/mysql
log_bin                                 = binlog
log_error                               = /var/log/mysql/error.log
log_slave_updates                       = ON
long_query_time                         = 60
loose-group_replication_allow_local_disjoint_gtids_join= ON
loose-group_replication_bootstrap_group = OFF
loose-group_replication_enforce_update_everywhere_checks= ON
loose-group_replication_group_name      = ZZZZZZ-ZZZZZZ-ZZZZZZ-ZZZZZZ
loose-group_replication_group_seeds     = BBB.0.0.000:33061,AA.AAA.AA.A:33061
loose-group_replication_ip_whitelist    = BBB.0.0.000,AA.AAA.AA.A,AA.0.0.000
loose-group_replication_local_address   = BBB.0.0.000:33061
loose-group_replication_recovery_use_ssl= 1
loose-group_replication_single_primary_mode= OFF
loose-group_replication_ssl_mode        = REQUIRED
loose-group_replication_start_on_boot   = OFF
master_info_repository                  = TABLE
max_allowed_packet                      = 16M
max_binlog_size                         = 100M
max_connect_errors                      = 100000000
pid-file                                = /var/run/mysqld/mysqld.pid
port                                    = 3306
relay_log                               = second-server-relay-bin
relay_log_info_repository               = TABLE
report_host                             = BB.BBB.BB.B
server_id                               = 2
skip_external_locking
slow_query_log                          = 1
slow_query_log_file                     = /var/log/mysql/slow_query.log
socket                                  = /var/run/mysqld/mysqld.sock
thread_cache_size                       = 8
thread_stack                            = 192K
tmpdir                                  = /tmp
transaction_write_set_extraction        = XXHASH64
user                                    = mysql

[mysqldump]
max_allowed_packet                      = 16M
quick
quote_names

[mysql]
no_auto_rehash

[isamchk]
key_buffer_size                         = 16M

[client]
port                                    = 3306
socket                                  = /var/run/mysqld/mysqld.sock

!includedir /etc/mysql/conf.d/

两台服务器都启动了，错误日志中没有错误。

3) 现在我尝试引导组:

在第一个服务器上:

  mysql> SET GLOBAL GROUP_REPLICATION_BOOTSTRAP_GROUP=ON;
Query OK, 0 rows affected (0.00 sec)

mysql> START GROUP_REPLICATION;
Query OK, 0 rows affected (2.11 sec)

mysql> SET GLOBAL GROUP_REPLICATION_BOOTSTRAP_GROUP=OFF;
Query OK, 0 rows affected (0.00 sec)

mysql> SELECT * FROM performance_schema.replication_group_members;
+---------------------------+--------------------------------------+-------------+-------------+--------------+
| CHANNEL_NAME              | MEMBER_ID                            | MEMBER_HOST | MEMBER_PORT | MEMBER_STATE |
+---------------------------+--------------------------------------+-------------+-------------+--------------+
| group_replication_applier | 111-111-111-111-111111-111111-111111 | AA.AAA.AA.A |        3306 | ONLINE       |
+---------------------------+--------------------------------------+-------------+-------------+--------------+
1 row in set (0.00 sec)

这看起来不错，日志文件中没有错误。

在第二台服务器上:

mysql> START GROUP_REPLICATION;
ERROR 3092 (HY000): The server is not configured properly to be an active member of the group. Please see more details on error log.
mysql> SELECT * FROM performance_schema.replication_group_members;
+---------------------------+--------------------------------------+-----------------+-------------+--------------+
| CHANNEL_NAME              | MEMBER_ID                            | MEMBER_HOST     | MEMBER_PORT | MEMBER_STATE |
+---------------------------+--------------------------------------+-----------------+-------------+--------------+
| group_replication_applier | 222-222-222-222-222222-222222-222222 | BBB.BBB.BBB.BBB |        3306 | OFFLINE      |
+---------------------------+--------------------------------------+-----------------+-------------+--------------+
1 row in set (0.00 sec)

在日志文件中，我可以看到组复制成功启动，第二台服务器连接到它自己 (BBB.0.0.000:33061) 和第一台服务器 (AA.AAA.AA.A:33061) -- “使用 SSL 连接成功”——但在我收到以下两个错误后立即出现:[GCS] 等待组通信引擎准备就绪时超时! [GCS] 群组通信引擎尚未准备好让成员加入。本地端口:33061

2018-04-15T00:15:05.987696Z 5 [Note] '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=''.
2018-04-15T00:15:05.990639Z 3 [Note] Plugin group_replication reported: 'Group Replication applier module successfully initialized!'
2018-04-15T00:15:05.990714Z 3 [Note] Plugin group_replication reported: 'auto_increment_increment is set to 7'
2018-04-15T00:15:05.990754Z 3 [Note] Plugin group_replication reported: 'auto_increment_offset is set to 1'
2018-04-15T00:15:05.990866Z 8 [Note] Slave SQL thread for channel 'group_replication_applier' initialized, starting replication in log 'FIRST' at position 0, relay log './second-server-relay-bin-group_replication_applier.000012' position: 4
2018-04-15T00:15:05.991232Z 0 [Note] Plugin group_replication reported: 'state 0 action xa_init'
2018-04-15T00:15:06.013709Z 0 [Note] Plugin group_replication reported: 'Successfully bound to 0.0.0.0:33061 (socket=51).'
2018-04-15T00:15:06.013787Z 0 [Note] Plugin group_replication reported: 'Successfully set listen backlog to 32 (socket=51)!'
2018-04-15T00:15:06.013827Z 0 [Note] Plugin group_replication reported: 'Successfully unblocked socket (socket=51)!'
2018-04-15T00:15:06.013876Z 0 [Note] Plugin group_replication reported: 'connecting to BBB.0.0.000 33061'
2018-04-15T00:15:06.013989Z 0 [Note] Plugin group_replication reported: 'client connected to BBB.0.0.000 33061 fd 52'
2018-04-15T00:15:06.014094Z 0 [Note] Plugin group_replication reported: 'Trying to connect using SSL.'
2018-04-15T00:15:06.014188Z 0 [Note] Plugin group_replication reported: 'Ready to accept incoming connections on 0.0.0.0:33061 (socket=51)!'
2018-04-15T00:15:06.027381Z 0 [Note] Plugin group_replication reported: 'Success connecting using SSL.'
2018-04-15T00:15:06.027583Z 0 [Note] Plugin group_replication reported: 'connecting to BBB.0.0.000 33061'
2018-04-15T00:15:06.027665Z 0 [Note] Plugin group_replication reported: 'client connected to BBB.0.0.000 33061 fd 62'
2018-04-15T00:15:06.027730Z 0 [Note] Plugin group_replication reported: 'Trying to connect using SSL.'
2018-04-15T00:15:06.040561Z 0 [Note] Plugin group_replication reported: 'Success connecting using SSL.'
2018-04-15T00:15:06.040752Z 0 [Note] Plugin group_replication reported: 'connecting to BBB.0.0.000 33061'
2018-04-15T00:15:06.040831Z 0 [Note] Plugin group_replication reported: 'client connected to BBB.0.0.000 33061 fd 66'
2018-04-15T00:15:06.040894Z 0 [Note] Plugin group_replication reported: 'Trying to connect using SSL.'
2018-04-15T00:15:06.053675Z 0 [Note] Plugin group_replication reported: 'Success connecting using SSL.'
2018-04-15T00:15:06.053889Z 0 [Note] Plugin group_replication reported: 'connecting to BBB.0.0.000 33061'
2018-04-15T00:15:06.053975Z 0 [Note] Plugin group_replication reported: 'client connected to BBB.0.0.000 33061 fd 70'
2018-04-15T00:15:06.054045Z 0 [Note] Plugin group_replication reported: 'Trying to connect using SSL.'
2018-04-15T00:15:06.067043Z 0 [Note] Plugin group_replication reported: 'Success connecting using SSL.'
2018-04-15T00:15:06.067228Z 0 [Note] Plugin group_replication reported: 'connecting to BBB.0.0.000 33061'
2018-04-15T00:15:06.067305Z 0 [Note] Plugin group_replication reported: 'client connected to BBB.0.0.000 33061 fd 74'
2018-04-15T00:15:06.067368Z 0 [Note] Plugin group_replication reported: 'Trying to connect using SSL.'
2018-04-15T00:15:06.080143Z 0 [Note] Plugin group_replication reported: 'Success connecting using SSL.'
2018-04-15T00:15:06.080326Z 0 [Note] Plugin group_replication reported: 'connecting to BBB.0.0.000 33061'
2018-04-15T00:15:06.080403Z 0 [Note] Plugin group_replication reported: 'client connected to BBB.0.0.000 33061 fd 78'
2018-04-15T00:15:06.080465Z 0 [Note] Plugin group_replication reported: 'Trying to connect using SSL.'
2018-04-15T00:15:06.093262Z 0 [Note] Plugin group_replication reported: 'Success connecting using SSL.'
2018-04-15T00:15:06.093460Z 0 [Note] Plugin group_replication reported: 'connecting to AA.AAA.AA.A 33061'
2018-04-15T00:15:06.125679Z 0 [Note] Plugin group_replication reported: 'client connected to AA.AAA.AA.A 33061 fd 82'
2018-04-15T00:15:06.125774Z 0 [Note] Plugin group_replication reported: 'Trying to connect using SSL.'
2018-04-15T00:15:06.204717Z 0 [Note] Plugin group_replication reported: 'Success connecting using SSL.'
2018-04-15T00:15:36.270721Z 0 [ERROR] Plugin group_replication reported: '[GCS] Timeout while waiting for the group communication engine to be ready!'
2018-04-15T00:15:36.270933Z 0 [ERROR] Plugin group_replication reported: '[GCS] The group communication engine is not ready for the member to join. Local port: 33061'
2018-04-15T00:15:36.271093Z 0 [Note] Plugin group_replication reported: 'state 4337 action xa_terminate'
2018-04-15T00:15:36.271158Z 0 [Note] Plugin group_replication reported: 'new state x_start'
2018-04-15T00:15:36.271210Z 0 [Note] Plugin group_replication reported: 'state 4337 action xa_exit'
2018-04-15T00:15:36.271331Z 0 [Note] Plugin group_replication reported: 'Exiting xcom thread'
2018-04-15T00:15:36.271383Z 0 [Note] Plugin group_replication reported: 'new state x_start'
2018-04-15T00:15:36.273406Z 0 [Warning] Plugin group_replication reported: 'read failed'
2018-04-15T00:15:36.281153Z 0 [ERROR] Plugin group_replication reported: '[GCS] The member was unable to join the group. Local port: 33061'
2018-04-15T00:16:05.990871Z 3 [ERROR] Plugin group_replication reported: 'Timeout on wait for view after joining group'
2018-04-15T00:16:05.991036Z 3 [Note] Plugin group_replication reported: 'Requesting to leave the group despite of not being a member'
2018-04-15T00:16:05.991118Z 3 [ERROR] Plugin group_replication reported: '[GCS] The member is leaving a group without being on one.'
2018-04-15T00:16:05.991182Z 0 [Note] Plugin group_replication reported: 'Destroying SSL'
2018-04-15T00:16:05.991242Z 0 [Note] Plugin group_replication reported: 'Success destroying SSL'
2018-04-15T00:16:05.991352Z 3 [Note] Plugin group_replication reported: 'auto_increment_increment is reset to 1'
2018-04-15T00:16:05.991408Z 3 [Note] Plugin group_replication reported: 'auto_increment_offset is reset to 1'
2018-04-15T00:16:05.991618Z 8 [Note] Error reading relay log event for channel 'group_replication_applier': slave SQL thread was killed
2018-04-15T00:16:05.992230Z 5 [Note] Plugin group_replication reported: 'The group replication applier thread was killed'

当我回到 FIRST 服务器时，日志中没有任何变化，它们与之前完全相同。

我找不到关于这两个错误的任何有用信息:“等待组通信引擎准备就绪时超时!”和“群组通信引擎尚未准备好让成员加入。本地端口:33061”

有没有人以前见过这个并且知道它表示什么？

最佳答案

事实证明这是一个网络问题。我不需要混合使用内部 IP 和公共(public) IP，而是只需要使用公共(public) IP。此外，我需要运行 ifconfig 命令来绑定(bind)服务器的公共(public) IP。

在每台服务器上，我运行“ifconfig”来识别网络端点的名称。然后我运行“ifcongig ntwk 00.00.00.00”:

 @FirstServer> ifconfig
 en1       Link encap:Ethernet  HWaddr 00:00:00:00:00:00  
           inet addr:00.00.00.00  Bcast:00.00.00.255  Mask:255.255.255.0
           inet6 addr: 00::00:00:00:00/64 Scope:Link
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:718094 errors:0 dropped:104 overruns:0 frame:0
           TX packets:708888 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000 
           RX bytes:666094518 (666.0 MB)  TX bytes:493309981 (493.3 MB)

 lo        Link encap:Local Loopback  
           inet addr:127.0.0.1  Mask:255.0.0.0
           inet6 addr: ::1/128 Scope:Host
           UP LOOPBACK RUNNING  MTU:65536  Metric:1
           RX packets:46526 errors:0 dropped:0 overruns:0 frame:0
           TX packets:46526 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1 
           RX bytes:13353180 (13.3 MB)  TX bytes:13353180 (13.3 MB)


@FirstServer> sudo ifconfig en1:1 AA.AAA.AA.A

第二个服务器:

 @SecondServer> ifconfig
 MyNets    Link encap:Ethernet  HWaddr 00:00:00:00:00:00  
           inet addr:00.00.00.00  Bcast:00.00.00.255  Mask:255.255.255.0
           inet6 addr: 00::00:00:00:00/64 Scope:Link
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:718094 errors:0 dropped:104 overruns:0 frame:0
           TX packets:708888 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000 
           RX bytes:666094518 (666.0 MB)  TX bytes:493309981 (493.3 MB)

 lo        Link encap:Local Loopback  
           inet addr:127.0.0.1  Mask:255.0.0.0
           inet6 addr: ::1/128 Scope:Host
           UP LOOPBACK RUNNING  MTU:65536  Metric:1
           RX packets:46526 errors:0 dropped:0 overruns:0 frame:0
           TX packets:46526 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1 
           RX bytes:13353180 (13.3 MB)  TX bytes:13353180 (13.3 MB)


@SecondServer> sudo ifconfig MyNets:1 BBB.BBB.BBB.BBB

绑定(bind)到公共(public) IP 地址后，我更新了配置文件。第一个服务器配置文件是:

[mysqld_safe]
nice                                    = 0
socket                                  = /var/run/mysqld/mysqld.sock

[mysqld]
basedir                                 = /usr
bind_address                            = 0.0.0.0
binlog_checksum                         = NONE
binlog_format                           = ROW
datadir                                 = /var/lib/mysql
enforce_gtid_consistency                = ON
general_log                             = 1
general_log_file                        = /var/log/mysql/mysql.log
gtid_mode                               = ON
key_buffer_size                         = 8388608
lc_messages_dir                         = /usr/share/mysql
log_bin                                 = binlog
log_error                               = /var/log/mysql/error.log
log_slave_updates                       = ON
long_query_time                         = 60
loose-group_replication_allow_local_disjoint_gtids_join= ON
loose-group_replication_bootstrap_group = OFF
loose-group_replication_enforce_update_everywhere_checks= ON
loose-group_replication_group_name      = ZZZZZZ-ZZZZZZ-ZZZZZZ-ZZZZZZ
loose-group_replication_group_seeds     = AA.AAA.AA.A:33061,BBB.BBB.BBB.BBB:33061
loose-group_replication_ip_whitelist    = AA.AAA.AA.A,BBB.BBB.BBB.BBB
loose-group_replication_local_address   = AA.AAA.AA.A:33061
loose-group_replication_recovery_use_ssl= 1
loose-group_replication_single_primary_mode= OFF
loose-group_replication_ssl_mode        = REQUIRED
loose-group_replication_start_on_boot   = OFF
master_info_repository                  = TABLE
max_allowed_packet                      = 16M
max_binlog_size                         = 100M
max_connect_errors                      = 100000000
pid-file                                = /var/run/mysqld/mysqld.pid
port                                    = 3306
relay_log                               = first-server-relay-bin
relay_log_info_repository               = TABLE
report_host                             = AA.AAA.AA.A
server_id                               = 1
skip_external_locking
slow_query_log                          = 1
slow_query_log_file                     = /var/log/mysql/slow_query.log
socket                                  = /var/run/mysqld/mysqld.sock
thread_cache_size                       = 8
thread_stack                            = 192K
tmpdir                                  = /tmp
transaction_write_set_extraction        = XXHASH64
user                                    = mysql

[mysqldump]
max_allowed_packet                      = 16M
quick
quote_names

[mysql]
no_auto_rehash

[isamchk]
key_buffer_size                         = 16M

[client]
port                                    = 3306
socket                                  = /var/run/mysqld/mysqld.sock

!includedir /etc/mysql/conf.d/

第二个服务器配置文件是:

[mysqld_safe]
nice                                    = 0
socket                                  = /var/run/mysqld/mysqld.sock

[mysqld]
basedir                                 = /usr
bind_address                            = 0.0.0.0
binlog_checksum                         = NONE
binlog_format                           = ROW
datadir                                 = /var/lib/mysql
enforce_gtid_consistency                = ON
general_log                             = 1
general_log_file                        = /var/log/mysql/mysql.log
gtid_mode                               = ON
key_buffer_size                         = 8388608
lc_messages_dir                         = /usr/share/mysql
log_bin                                 = binlog
log_error                               = /var/log/mysql/error.log
log_slave_updates                       = ON
long_query_time                         = 60
loose-group_replication_allow_local_disjoint_gtids_join= ON
loose-group_replication_bootstrap_group = OFF
loose-group_replication_enforce_update_everywhere_checks= ON
loose-group_replication_group_name      = ZZZZZZ-ZZZZZZ-ZZZZZZ-ZZZZZZ
loose-group_replication_group_seeds     = BB.BBB.BB.B:33061,AA.AAA.AA.A:33061
loose-group_replication_ip_whitelist    = BB.BBB.BB.B,AA.AAA.AA.A
loose-group_replication_local_address   = BB.BBB.BB.B:33061
loose-group_replication_recovery_use_ssl= 1
loose-group_replication_single_primary_mode= OFF
loose-group_replication_ssl_mode        = REQUIRED
loose-group_replication_start_on_boot   = OFF
master_info_repository                  = TABLE
max_allowed_packet                      = 16M
max_binlog_size                         = 100M
max_connect_errors                      = 100000000
pid-file                                = /var/run/mysqld/mysqld.pid
port                                    = 3306
relay_log                               = second-server-relay-bin
relay_log_info_repository               = TABLE
report_host                             = BB.BBB.BB.B
server_id                               = 2
skip_external_locking
slow_query_log                          = 1
slow_query_log_file                     = /var/log/mysql/slow_query.log
socket                                  = /var/run/mysqld/mysqld.sock
thread_cache_size                       = 8
thread_stack                            = 192K
tmpdir                                  = /tmp
transaction_write_set_extraction        = XXHASH64
user                                    = mysql

[mysqldump]
max_allowed_packet                      = 16M
quick
quote_names

[mysql]
no_auto_rehash

[isamchk]
key_buffer_size                         = 16M

[client]
port                                    = 3306
socket                                  = /var/run/mysqld/mysqld.sock

!includedir /etc/mysql/conf.d/

最后，在第一台服务器上，我重新启动了 mysql，登录并运行了以下命令:

mysql> SET GLOBAL GROUP_REPLICATION_BOOTSTRAP_GROUP=ON;
Query OK, 0 rows affected (0.00 sec)

mysql> START GROUP_REPLICATION;
Query OK, 0 rows affected (2.11 sec)

mysql> SET GLOBAL GROUP_REPLICATION_BOOTSTRAP_GROUP=OFF;
Query OK, 0 rows affected (0.00 sec)

mysql> SELECT * FROM performance_schema.replication_group_members;
+---------------------------+--------------------------------------+-------------+-------------+--------------+
| CHANNEL_NAME              | MEMBER_ID                            | MEMBER_HOST | MEMBER_PORT | MEMBER_STATE |
+---------------------------+--------------------------------------+-------------+-------------+--------------+
| group_replication_applier | 111-111-111-111-111111-111111-111111 | AA.AAA.AA.A |        3306 | ONLINE       |
+---------------------------+--------------------------------------+-------------+-------------+--------------+
1 row in set (0.00 sec)

在第二台服务器上，我重新启动了 mysql，登录并运行了以下命令:

mysql> START GROUP_REPLICATION;
Query OK, 0 rows affected (2.11 sec)

mysql> SELECT * FROM performance_schema.replication_group_members;
+---------------------------+--------------------------------------+-------------+-------------+--------------+
| CHANNEL_NAME              | MEMBER_ID                            | MEMBER_HOST | MEMBER_PORT | MEMBER_STATE |
+---------------------------+--------------------------------------+-------------+-------------+--------------+
| group_replication_applier | 111-111-111-111-111111-111111-111111 | AA.AAA.AA.A |        3306 | ONLINE       |
+---------------------------+--------------------------------------+-------------+-------------+--------------+
| group_replication_applier | 111-111-111-111-111111-111111-111111 | BBB.BBB.BBB.BBB |    3306 | ONLINE       |
+---------------------------+--------------------------------------+-------------+-------------+--------------+
1 row in set (0.00 sec)

现在他们正在交流和连接!

关于MySQL 组复制 : Timeout while waiting for the group communication engine to be ready，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/49837554/

文章推荐： ios - 从 Cllocation 获取 CLLocationCorrdinate2D 时出错

文章推荐： ios - viewDidLoad 上的 CustomDelegate

文章推荐： php - 在 MySQL 连接上设置字符集不起作用

office-communicator - Office Communicator 在线状态如何工作？
我有兴趣了解有关 Microsoft Office Communicator 的更多信息IM 客户端，以及它如何确定您的存在(即您是在计算机旁还是不在)。任何人都可以向我指出解释这一点的教程或 API
python - .communicate() 和 .communicate()[0] 有什么区别？
我正在使用 python。我正在尝试运行一个进程并使用 subprocess.popen 获取输出。阅读周围后，我看到人们使用 communicate()[0] 但那不在文档中，它用于示例。我想知道是
python - .communicate() 和 .communicate()[0] 有什么区别？
我正在使用 python。我正在尝试运行一个进程并使用 subprocess.popen 获取输出。阅读周围后，我看到人们使用 communicate()[0] 但那不在文档中，它用于示例。我想知道是
Azure 计算模拟器错误 "The communication object ... cannot be used for communication because it is in the Faulted state."
我有一些设置和拆卸脚本，它们使用 csrun.exe 为一些自动化测试准备本地计算模拟器。 C:\Program Files\Microsoft SDKs\Azure\Emulator\csrun.e
go - 解释: Don't communicate by sharing memory; share memory by communicating
我想知道对这句名言最接地气的解释是什么: Don't communicate by sharing memory; share memory by communicating. (R. Pike) 在
communication - 无状态协议(protocol)的参数(上下文 : simple point-to-point communication)
(所以 this question has been asked before ，但在一般意义上，大多数响应都是在与多个服务器/客户端/等的一般网络通信的上下文中) 在简单的点对点通信协议(proto
python - boost.mpi.world Communicator 与 C++ 签名不匹配:boost::mpi::communicator
我正在尽力将 C++ 模块链接到 python 绑定(bind)。我正在努力实现 boost mpi 通信。我正在将 boost.mpi.world 对象发送到 C++，它需要一个 boost::mp
python - 为什么 `print foo.communicate()[0]` 与 `print foo.communicate()` 不同“
情况是这样的: 我有一个正在运行的命令: import subprocess foo = subprocess.Popen('ls /', shell=True, stdout=subprocess.
communication - 你为提高软技能所做的最有效的事情是什么？
关闭。这个问题是opinion-based .它目前不接受答案。想改善这个问题吗？更新问题，以便可以通过 editing this post 用事实和引文回答问题. 7年前关闭。 Improve t
communication - 你如何与你所在城市以外的团队沟通？
关闭。这个问题是off-topic .它目前不接受答案。想改进这个问题？ Update the question所以它是on-topic对于堆栈溢出。 10年前关闭。 Improve this qu
communication - 如何让员工更多地参与？
关闭。这个问题是opinion-based .它目前不接受答案。想改善这个问题吗？更新问题，以便可以通过 editing this post 用事实和引文回答问题. 2年前关闭。 Improve t
communication - 如何与客户进行良好的沟通
关闭。这个问题不符合Stack Overflow guidelines .它目前不接受答案。这个问题似乎与 help center 中定义的范围内的编程无关。 . 关闭 5 年前。 Improve
communication - 您是否出于工作目的在线聊天？
我曾与那些与同龄人在线聊天的人一起工作，他们不断地围绕想法进行讨论。我也曾与那些坚决拒绝并认为这是浪费时间的人一起工作。在线实时聊天论坛对您特别有用吗？为什么或者为什么不？在您的公司内部，还是在外
communication - 保持应用程序和基础设施连接
我在一个分为两组的 IT 部门工作。一组开发和管理应用程序，另一组管理公司的基础设施和服务器。我们面临的问题之一是沟通中断。我为应用程序组工作，我遇到的问题之一是当基础设施关闭服务器或刷新数据库时没有
communication - 优先考虑开发人员通信的即时消息
我的团队与 IM 进行了很多交流。我们有时甚至会使用 IM 向在下一个立方体中的人提问。这样做的原因是我们都发现接听 IM 的干扰比说话要少得多。尽管如此，我发现当我低头编码时，闪烁的消息窗口可能会
communication - 管理数字干扰的有效方法
按照目前的情况，这个问题不适合我们的问答形式。我们希望答案得到事实、引用或专业知识的支持，但这个问题可能会引发辩论、争论、投票或扩展讨论。如果您觉得这个问题可以改进并可能重新打开，visit the
communication - 改善软件团队成员之间沟通的方法
关闭。这个问题不满足Stack Overflow guidelines .它目前不接受答案。想改善这个问题吗？更新问题，使其成为 on-topic对于堆栈溢出。 4年前关闭。 Improve thi
communication - 密集的编程会降低沟通技巧？
关闭。这个问题是opinion-based .它目前不接受答案。想改善这个问题吗？更新问题，以便可以通过 editing this post 用事实和引文回答问题. 3年前关闭。 Improve t
communication - 客户参与敏捷开发的最佳实践？
关闭。这个问题是off-topic .它目前不接受答案。想改进这个问题？ Update the question所以它是on-topic对于堆栈溢出。 10年前关闭。 Improve this qu
communication - 汉明码是如何工作的？
传输数据时，汉明码显然允许您重新创建已通过线路损坏的数据(纠错码)。这是如何工作的，它的局限性是什么(如果有的话)？有没有更好的纠错解决方案(相对于重传)？是否存在重传更好的情况？最佳答案让我

行者123

个人简介

我是一名优秀的程序员,十分优秀！

作者热门文章

滴滴打车优惠券免费领取

全站热门文章

首页

博学

6Ren·AI

商城