从MGR集群到MGR集群的GTID复制

最新推荐文章于 2023-10-04 19:34:27 发布
最新推荐文章于 2023-10-04 19:34:27 发布
阅读量1.7k 收藏 2
点赞数 1
分类专栏： mysql 文章标签： mysql group replication GTID
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/windyzhou/article/details/80193879
版权
参见 《从MGR集群到单机的GTID复制》一文，已经验证了MGR集群到单机的复制，并确认主节点发生漂移时不影响数据复制，所以MGR到MGR的复制验证，目的是测试在从属MGR的主节点发生漂移时，复制是中断还是导致数据错乱，如果是中断，当从属MGR主节点切换回来时，复制是否可以继续。

为了方便描述，我们使用字母代码来标记实例：
主MGR有2个实例(机器内存不足，启动不了6个实例)：A、B，当前主节点为A
从属MGR有2个实例：D、E，当前主节点为D
已经建立了D从A复制数据

测试案例：
1、切换从属MGR的主节点到E
2、A上增加数据，在D、E上查看数据与复制状态

3、切换从属MGR的主节点回E，在D、E上查看数据与复制状态

在D上操作：

mysql> show slave status for channel 'normal_replication'\G
*************************** 1. row ***************************
               Slave_IO_State: Waiting for master to send event
                  Master_Host: 127.0.0.1
                  Master_User: repl
                  Master_Port: 24801
                Connect_Retry: 60
              Master_Log_File: binlog.000004
          Read_Master_Log_Pos: 3849
               Relay_Log_File: myserver01-relay-bin-normal_replication.000002
                Relay_Log_Pos: 389
        Relay_Master_Log_File: binlog.000004
             Slave_IO_Running: Yes
            Slave_SQL_Running: Yes
              Replicate_Do_DB: 
          Replicate_Ignore_DB: 
           Replicate_Do_Table: 
       Replicate_Ignore_Table: 
      Replicate_Wild_Do_Table: 
  Replicate_Wild_Ignore_Table: 
                   Last_Errno: 0
                   Last_Error: 
                 Skip_Counter: 0
          Exec_Master_Log_Pos: 3849
              Relay_Log_Space: 612
              Until_Condition: None
               Until_Log_File: 
                Until_Log_Pos: 0
           Master_SSL_Allowed: No
           Master_SSL_CA_File: 
           Master_SSL_CA_Path: 
              Master_SSL_Cert: 
            Master_SSL_Cipher: 
               Master_SSL_Key: 
        Seconds_Behind_Master: 0
Master_SSL_Verify_Server_Cert: No
                Last_IO_Errno: 0
                Last_IO_Error: 
               Last_SQL_Errno: 0
               Last_SQL_Error: 
  Replicate_Ignore_Server_Ids: 
             Master_Server_Id: 1
                  Master_UUID: 595937c0-4d9c-11e8-a819-00163e06ea60
             Master_Info_File: mysql.slave_master_info
                    SQL_Delay: 0
          SQL_Remaining_Delay: NULL
      Slave_SQL_Running_State: Slave has read all relay log; waiting for more updates
           Master_Retry_Count: 86400
                  Master_Bind: 
      Last_IO_Error_Timestamp: 
     Last_SQL_Error_Timestamp: 
               Master_SSL_Crl: 
           Master_SSL_Crlpath: 
           Retrieved_Gtid_Set: 
            Executed_Gtid_Set: aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa:1-26,
aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaab:1-3
                Auto_Position: 1
         Replicate_Rewrite_DB: 
                 Channel_Name: normal_replication
           Master_TLS_Version: 
1 row in set (0.02 sec)

mysql> stop group_replication;
Query OK, 0 rows affected (9.36 sec)

mysql> start group_replication;
Query OK, 0 rows affected (4.78 sec)

mysql> select * from performance_schema.replication_group_members;
+---------------------------+--------------------------------------+-------------+-------------+--------------+
| CHANNEL_NAME              | MEMBER_ID                            | MEMBER_HOST | MEMBER_PORT | MEMBER_STATE |
+---------------------------+--------------------------------------+-------------+-------------+--------------+
| group_replication_applier | 31ab6701-4ec3-11e8-a66b-00163e06ea60 | myserver01  |       24806 | ONLINE       |
| group_replication_applier | 9e4308df-4f44-11e8-b364-00163e06ea60 | myserver01  |       24804 | ONLINE       |
+---------------------------+--------------------------------------+-------------+-------------+--------------+
2 rows in set (0.08 sec)

mysql> show global status like 'group_replication%';
+----------------------------------+--------------------------------------+
| Variable_name                    | Value                                |
+----------------------------------+--------------------------------------+
| group_replication_primary_member | 31ab6701-4ec3-11e8-a66b-00163e06ea60 |
+----------------------------------+--------------------------------------+
1 row in set (0.11 sec)

mysql> show slave status for channel 'normal_replication'\G
*************************** 1. row ***************************
               Slave_IO_State: 
                  Master_Host: 127.0.0.1
                  Master_User: repl
                  Master_Port: 24801
                Connect_Retry: 60
              Master_Log_File: binlog.000004
          Read_Master_Log_Pos: 3849
               Relay_Log_File: myserver01-relay-bin-normal_replication.000002
                Relay_Log_Pos: 389
        Relay_Master_Log_File: binlog.000004
             Slave_IO_Running: No
            Slave_SQL_Running: No
              Replicate_Do_DB: 
          Replicate_Ignore_DB: 
           Replicate_Do_Table: 
       Replicate_Ignore_Table: 
      Replicate_Wild_Do_Table: 
  Replicate_Wild_Ignore_Table: 
                   Last_Errno: 0
                   Last_Error: 
                 Skip_Counter: 0
          Exec_Master_Log_Pos: 3849
              Relay_Log_Space: 612
              Until_Condition: None
               Until_Log_File: 
                Until_Log_Pos: 0
           Master_SSL_Allowed: No
           Master_SSL_CA_File: 
           Master_SSL_CA_Path: 
              Master_SSL_Cert: 
            Master_SSL_Cipher: 
               Master_SSL_Key: 
        Seconds_Behind_Master: NULL
Master_SSL_Verify_Server_Cert: No
                Last_IO_Errno: 0
                Last_IO_Error: 
               Last_SQL_Errno: 0
               Last_SQL_Error: 
  Replicate_Ignore_Server_Ids: 
             Master_Server_Id: 1
                  Master_UUID: 595937c0-4d9c-11e8-a819-00163e06ea60
             Master_Info_File: mysql.slave_master_info
                    SQL_Delay: 0
          SQL_Remaining_Delay: NULL
      Slave_SQL_Running_State: 
           Master_Retry_Count: 86400
                  Master_Bind: 
      Last_IO_Error_Timestamp: 
     Last_SQL_Error_Timestamp: 
               Master_SSL_Crl: 
           Master_SSL_Crlpath: 
           Retrieved_Gtid_Set: 
            Executed_Gtid_Set: aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa:1-26,
aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaab:1-4
                Auto_Position: 1
         Replicate_Rewrite_DB: 
                 Channel_Name: normal_replication
           Master_TLS_Version: 
1 row in set (0.02 sec)
可以看到切换后，从属MGR主节点D上的复制进程已经被自动停止了。

在A上操作： 
mysql> select * from test.t1;
+----+--------+
| c1 | c2     |
+----+--------+
|  1 | Luis   |
|  2 | from A |
|  3 | From A |
|  4 | From B |
|  5 | From A |
+----+--------+
5 rows in set (0.00 sec)

mysql> insert into test.t1 values(6,'From A');
Query OK, 1 row affected (0.02 sec)

mysql> select * from test.t1;
+----+--------+
| c1 | c2     |
+----+--------+
|  1 | Luis   |
|  2 | from A |
|  3 | From A |
|  4 | From B |
|  5 | From A |
|  6 | From A |
+----+--------+
6 rows in set (0.00 sec)

在D、E上操作：

mysql> select * from test.t1;
+----+--------+
| c1 | c2     |
+----+--------+
|  1 | Luis   |
|  2 | from A |
|  3 | From A |
|  4 | From B |
|  5 | From A |
+----+--------+
5 rows in set (0.00 sec)

mysql> start slave;
Query OK, 0 rows affected (0.01 sec)

mysql> show slave status for channel 'normal_replication'\G
*************************** 1. row ***************************
               Slave_IO_State: 
                  Master_Host: 127.0.0.1
                  Master_User: repl
                  Master_Port: 24801
                Connect_Retry: 60
              Master_Log_File: binlog.000004
          Read_Master_Log_Pos: 3849
               Relay_Log_File: myserver01-relay-bin-normal_replication.000002
                Relay_Log_Pos: 389
        Relay_Master_Log_File: binlog.000004
             Slave_IO_Running: No
            Slave_SQL_Running: No
              Replicate_Do_DB: 
          Replicate_Ignore_DB: 
           Replicate_Do_Table: 
       Replicate_Ignore_Table: 
      Replicate_Wild_Do_Table: 
  Replicate_Wild_Ignore_Table: 
                   Last_Errno: 1593
                   Last_Error: Fatal error: Failed to run 'applier_start' hook
                 Skip_Counter: 0
          Exec_Master_Log_Pos: 3849
              Relay_Log_Space: 612
              Until_Condition: None
               Until_Log_File: 
                Until_Log_Pos: 0
           Master_SSL_Allowed: No
           Master_SSL_CA_File: 
           Master_SSL_CA_Path: 
              Master_SSL_Cert: 
            Master_SSL_Cipher: 
               Master_SSL_Key: 
        Seconds_Behind_Master: NULL
Master_SSL_Verify_Server_Cert: No
                Last_IO_Errno: 1593
                Last_IO_Error: Fatal error: Failed to run 'thread_start' hook
               Last_SQL_Errno: 1593
               Last_SQL_Error: Fatal error: Failed to run 'applier_start' hook
  Replicate_Ignore_Server_Ids: 
             Master_Server_Id: 1
                  Master_UUID: 595937c0-4d9c-11e8-a819-00163e06ea60
             Master_Info_File: mysql.slave_master_info
                    SQL_Delay: 0
          SQL_Remaining_Delay: NULL
      Slave_SQL_Running_State: 
           Master_Retry_Count: 86400
                  Master_Bind: 
      Last_IO_Error_Timestamp: 180504 11:50:06
     Last_SQL_Error_Timestamp: 180504 11:50:06
               Master_SSL_Crl: 
           Master_SSL_Crlpath: 
           Retrieved_Gtid_Set: 
            Executed_Gtid_Set: aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa:1-26,
aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaab:1-4
                Auto_Position: 1
         Replicate_Rewrite_DB: 
                 Channel_Name: normal_replication
           Master_TLS_Version: 
1 row in set (0.00 sec)

mysql> select * from test.t1;
+----+--------+
| c1 | c2     |
+----+--------+
|  1 | Luis   |
|  2 | from A |
|  3 | From A |
|  4 | From B |
|  5 | From A |
+----+--------+
5 rows in set (0.00 sec)
数据是过不来的，在D节点上启动slave进程也会因为当前状态为从节点没有启动。验证结果，D、E数据一致，在主MGR的数据无法过来。

在E上操作：

mysql> stop group_replication;
Query OK, 0 rows affected (9.43 sec)

mysql> start group_replication;
Query OK, 0 rows affected (4.92 sec)

mysql> select * from performance_schema.replication_group_members;
+---------------------------+--------------------------------------+-------------+-------------+--------------+
| CHANNEL_NAME              | MEMBER_ID                            | MEMBER_HOST | MEMBER_PORT | MEMBER_STATE |
+---------------------------+--------------------------------------+-------------+-------------+--------------+
| group_replication_applier | 31ab6701-4ec3-11e8-a66b-00163e06ea60 | myserver01  |       24806 | ONLINE       |
| group_replication_applier | 9e4308df-4f44-11e8-b364-00163e06ea60 | myserver01  |       24804 | ONLINE       |
+---------------------------+--------------------------------------+-------------+-------------+--------------+
2 rows in set (0.00 sec)

mysql> show global status like 'group_replication%';
+----------------------------------+--------------------------------------+
| Variable_name                    | Value                                |
+----------------------------------+--------------------------------------+
| group_replication_primary_member | 9e4308df-4f44-11e8-b364-00163e06ea60 |
+----------------------------------+--------------------------------------+
1 row in set (0.01 sec)

把从属MGR的主节点切换回D。

在D上操作：

mysql> show slave status for channel 'normal_replication'\G
*************************** 1. row ***************************
               Slave_IO_State: 
                  Master_Host: 127.0.0.1
                  Master_User: repl
                  Master_Port: 24801
                Connect_Retry: 60
              Master_Log_File: binlog.000004
          Read_Master_Log_Pos: 3849
               Relay_Log_File: myserver01-relay-bin-normal_replication.000002
                Relay_Log_Pos: 389
        Relay_Master_Log_File: binlog.000004
             Slave_IO_Running: No
            Slave_SQL_Running: No
              Replicate_Do_DB: 
          Replicate_Ignore_DB: 
           Replicate_Do_Table: 
       Replicate_Ignore_Table: 
      Replicate_Wild_Do_Table: 
  Replicate_Wild_Ignore_Table: 
                   Last_Errno: 1593
                   Last_Error: Fatal error: Failed to run 'applier_start' hook
                 Skip_Counter: 0
          Exec_Master_Log_Pos: 3849
              Relay_Log_Space: 612
              Until_Condition: None
               Until_Log_File: 
                Until_Log_Pos: 0
           Master_SSL_Allowed: No
           Master_SSL_CA_File: 
           Master_SSL_CA_Path: 
              Master_SSL_Cert: 
            Master_SSL_Cipher: 
               Master_SSL_Key: 
        Seconds_Behind_Master: NULL
Master_SSL_Verify_Server_Cert: No
                Last_IO_Errno: 1593
                Last_IO_Error: Fatal error: Failed to run 'thread_start' hook
               Last_SQL_Errno: 1593
               Last_SQL_Error: Fatal error: Failed to run 'applier_start' hook
  Replicate_Ignore_Server_Ids: 
             Master_Server_Id: 1
                  Master_UUID: 595937c0-4d9c-11e8-a819-00163e06ea60
             Master_Info_File: mysql.slave_master_info
                    SQL_Delay: 0
          SQL_Remaining_Delay: NULL
      Slave_SQL_Running_State: 
           Master_Retry_Count: 86400
                  Master_Bind: 
      Last_IO_Error_Timestamp: 180504 11:50:06
     Last_SQL_Error_Timestamp: 180504 11:50:06
               Master_SSL_Crl: 
           Master_SSL_Crlpath: 
           Retrieved_Gtid_Set: 
            Executed_Gtid_Set: aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa:1-26,
aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaab:1-5
                Auto_Position: 1
         Replicate_Rewrite_DB: 
                 Channel_Name: normal_replication
           Master_TLS_Version: 
1 row in set (0.02 sec)

mysql> start slave;
Query OK, 0 rows affected (0.03 sec)

mysql> show slave status for channel 'normal_replication'\G
*************************** 1. row ***************************
               Slave_IO_State: Waiting for master to send event
                  Master_Host: 127.0.0.1
                  Master_User: repl
                  Master_Port: 24801
                Connect_Retry: 60
              Master_Log_File: binlog.000004
          Read_Master_Log_Pos: 4093
               Relay_Log_File: myserver01-relay-bin-normal_replication.000003
                Relay_Log_Pos: 633
        Relay_Master_Log_File: binlog.000004
             Slave_IO_Running: Yes
            Slave_SQL_Running: Yes
              Replicate_Do_DB: 
          Replicate_Ignore_DB: 
           Replicate_Do_Table: 
       Replicate_Ignore_Table: 
      Replicate_Wild_Do_Table: 
  Replicate_Wild_Ignore_Table: 
                   Last_Errno: 0
                   Last_Error: 
                 Skip_Counter: 0
          Exec_Master_Log_Pos: 4093
              Relay_Log_Space: 1095
              Until_Condition: None
               Until_Log_File: 
                Until_Log_Pos: 0
           Master_SSL_Allowed: No
           Master_SSL_CA_File: 
           Master_SSL_CA_Path: 
              Master_SSL_Cert: 
            Master_SSL_Cipher: 
               Master_SSL_Key: 
        Seconds_Behind_Master: 0
Master_SSL_Verify_Server_Cert: No
                Last_IO_Errno: 0
                Last_IO_Error: 
               Last_SQL_Errno: 0
               Last_SQL_Error: 
  Replicate_Ignore_Server_Ids: 
             Master_Server_Id: 1
                  Master_UUID: 595937c0-4d9c-11e8-a819-00163e06ea60
             Master_Info_File: mysql.slave_master_info
                    SQL_Delay: 0
          SQL_Remaining_Delay: NULL
      Slave_SQL_Running_State: Slave has read all relay log; waiting for more updates
           Master_Retry_Count: 86400
                  Master_Bind: 
      Last_IO_Error_Timestamp: 
     Last_SQL_Error_Timestamp: 
               Master_SSL_Crl: 
           Master_SSL_Crlpath: 
           Retrieved_Gtid_Set: aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa:27
            Executed_Gtid_Set: aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa:1-27,
aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaab:1-5
                Auto_Position: 1
         Replicate_Rewrite_DB: 
                 Channel_Name: normal_replication
           Master_TLS_Version: 
1 row in set (0.00 sec)

mysql> select * from test.t1;
+----+--------+
| c1 | c2     |
+----+--------+
|  1 | Luis   |
|  2 | from A |
|  3 | From A |
|  4 | From B |
|  5 | From A |
|  6 | From A |
+----+--------+
6 rows in set (0.00 sec)
当从属MGR主节点切换回D后，启动slave进程，数据开始恢复同步。


最后，我们附加测试一下两个MGR之间的双向复制，用于两个机房做机房级别的故障切换。如果方案可行，可做为机房双活方案，需要加上DNS的切换，平时DNS使用主机房VIP，故障切换时，使用备用机房VIP，重启应用。

测试方案：
1、配置双向复制，查看两个方向加数据是否可以同步
2、把从属MGR设置super_read_only超级只读，是否可以同步

在A上操作： 
mysql> select * from test.t1;
+----+--------+
| c1 | c2     |
+----+--------+
|  1 | Luis   |
|  2 | from A |
|  3 | From A |
|  4 | From B |
|  5 | From A |
|  6 | From A |
+----+--------+
6 rows in set (0.02 sec)

mysql> insert into test.t1 values(7,'From A');
Query OK, 1 row affected (0.01 sec)

mysql> select * from test.t1;
+----+--------+
| c1 | c2     |
+----+--------+
|  1 | Luis   |
|  2 | from A |
|  3 | From A |
|  4 | From B |
|  5 | From A |
|  6 | From A |
|  7 | From A |
+----+--------+
7 rows in set (0.00 sec)

在D上操作：

mysql> select * from test.t1;
+----+--------+
| c1 | c2     |
+----+--------+
|  1 | Luis   |
|  2 | from A |
|  3 | From A |
|  4 | From B |
|  5 | From A |
|  6 | From A |
|  7 | From A |
+----+--------+
7 rows in set (0.00 sec)

mysql> insert into test.t1 values(8,'From D');
Query OK, 1 row affected (0.01 sec)

mysql> select * from test.t1;
+----+--------+
| c1 | c2     |
+----+--------+
|  1 | Luis   |
|  2 | from A |
|  3 | From A |
|  4 | From B |
|  5 | From A |
|  6 | From A |
|  7 | From A |
|  8 | From D |
+----+--------+
8 rows in set (0.00 sec)

在A上操作：

mysql> select * from test.t1;
+----+--------+
| c1 | c2     |
+----+--------+
|  1 | Luis   |
|  2 | from A |
|  3 | From A |
|  4 | From B |
|  5 | From A |
|  6 | From A |
|  7 | From A |
|  8 | From D |
+----+--------+
8 rows in set (0.00 sec)
验证双向复制是可行的。

在D上操作：

mysql> show global variables like '%read_only';
+-----------------------+-------+
| Variable_name         | Value |
+-----------------------+-------+
| innodb_read_only      | OFF   |
| read_only             | OFF   |
| super_read_only       | OFF   |
| transaction_read_only | OFF   |
| tx_read_only          | OFF   |
+-----------------------+-------+
5 rows in set (0.00 sec)

mysql> set global read_only=on;
Query OK, 0 rows affected (0.00 sec)

mysql> set global super_read_only=on;
Query OK, 0 rows affected (0.00 sec)

mysql> show global variables like '%read_only';
+-----------------------+-------+
| Variable_name         | Value |
+-----------------------+-------+
| innodb_read_only      | OFF   |
| read_only             | ON    |
| super_read_only       | ON    |
| transaction_read_only | OFF   |
| tx_read_only          | OFF   |
+-----------------------+-------+
5 rows in set (0.00 sec)

mysql> insert into test.t1 values(9,'From D');
ERROR 1290 (HY000): The MySQL server is running with the --super-read-only option so it cannot execute this statement

mysql> show slave status\G
*************************** 1. row ***************************
               Slave_IO_State: Waiting for master to send event
                  Master_Host: 127.0.0.1
                  Master_User: repl
                  Master_Port: 24801
                Connect_Retry: 60
              Master_Log_File: binlog.000005
          Read_Master_Log_Pos: 3096
               Relay_Log_File: myserver01-relay-bin-normal_replication.000004
                Relay_Log_Pos: 1476
        Relay_Master_Log_File: binlog.000005
             Slave_IO_Running: Yes
            Slave_SQL_Running: Yes
              Replicate_Do_DB: 
          Replicate_Ignore_DB: 
           Replicate_Do_Table: 
       Replicate_Ignore_Table: 
      Replicate_Wild_Do_Table: 
  Replicate_Wild_Ignore_Table: 
                   Last_Errno: 0
                   Last_Error: 
                 Skip_Counter: 0
          Exec_Master_Log_Pos: 3096
              Relay_Log_Space: 2182
              Until_Condition: None
               Until_Log_File: 
                Until_Log_Pos: 0
           Master_SSL_Allowed: No
           Master_SSL_CA_File: 
           Master_SSL_CA_Path: 
              Master_SSL_Cert: 
            Master_SSL_Cipher: 
               Master_SSL_Key: 
        Seconds_Behind_Master: 0
Master_SSL_Verify_Server_Cert: No
                Last_IO_Errno: 0
                Last_IO_Error: 
               Last_SQL_Errno: 0
               Last_SQL_Error: 
  Replicate_Ignore_Server_Ids: 
             Master_Server_Id: 1
                  Master_UUID: 595937c0-4d9c-11e8-a819-00163e06ea60
             Master_Info_File: mysql.slave_master_info
                    SQL_Delay: 0
          SQL_Remaining_Delay: NULL
      Slave_SQL_Running_State: Slave has read all relay log; waiting for more updates
           Master_Retry_Count: 86400
                  Master_Bind: 
      Last_IO_Error_Timestamp: 
     Last_SQL_Error_Timestamp: 
               Master_SSL_Crl: 
           Master_SSL_Crlpath: 
           Retrieved_Gtid_Set: aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa:27-30
            Executed_Gtid_Set: aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa:1-30,
aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaab:1-6
                Auto_Position: 1
         Replicate_Rewrite_DB: 
                 Channel_Name: normal_replication
           Master_TLS_Version: 
1 row in set (0.00 sec)

在A上操作：

mysql> insert into test.t1 values(9,'From A');
Query OK, 1 row affected (0.31 sec)

mysql> select * from test.t1;
+----+--------+
| c1 | c2     |
+----+--------+
|  1 | Luis   |
|  2 | from A |
|  3 | From A |
|  4 | From B |
|  5 | From A |
|  6 | From A |
|  7 | From A |
|  8 | From D |
|  9 | From A |
+----+--------+
9 rows in set (0.19 sec)

在D上操作：

mysql> select * from test.t1;
+----+--------+
| c1 | c2     |
+----+--------+
|  1 | Luis   |
|  2 | from A |
|  3 | From A |
|  4 | From B |
|  5 | From A |
|  6 | From A |
|  7 | From A |
|  8 | From D |
|  9 | From A |
+----+--------+
9 rows in set (0.12 sec)
验证结果是可以在从属MGR上设置super_read_only，在不影响复制的情况下拒绝错误的写请求。







windyzhou
关注
专栏目录
mysql 8 MGR集群
11-14
MySQL 8 MGR 集群 MySQL 8 MGR 集群是一种高可用性的数据库解决方案，通过在多个服务器上部署多个 MySQL 实例，实现数据库的高可用性和负载均衡。本文将详细介绍 MySQL 8 MGR 集群的原理、安装、配置和部署。 一、...
Semisynch: Last_IO_Error: Fatal error: Failed to run 'after_queue_event' hook
fs20041242的专栏
02-21 788
Description: When executing a replication workload with semisynch replication turned off and periodic STOP SLAVE IO_THREAD thread, START SLAVE IO_THREAD (in order to simulate network failures), the...
从MGR集群到单机的GTID复制
windyzhou的专栏
05-04 614
为了方便描述，我们使用字母代码来标记实例：群组有3个实例：A、B、C单节点实例为D当前主节点为A，在群组集群主节点上配置普通复制slave专用用户：CREATE USER repl@'%' IDENTIFIED BY 'repl'; GRANT REPLICATION SLAVE ON *.* TO repl@'%';在单节点上配置到主节点的复制，5.7上建议设置channel名称：CHANGE ...
mysql mgr数据不一致_MGR主从不一致问题排查与修复
weixin_39929723的博客
01-28 699
运行环境linux：CentOS release 6.8 (Final)kernel：2.6.32-642.6.2.el6.x86_64mysql Server version: 5.7.21-20-log Percona Server (GPL)，MGR单主模式1.故障现象解析binlogmysqlbinlog -v --base64-output=DECODE-ROWS mysql-bin.0...
深度分析 | MGR相同GTID产生不同transaction故障分析
ActionTech的博客
03-23 680
前 言 本文是由爱可生运维团队出品的「MySQL专栏」系列文章，内容来自于运维团队一线实战经验，涵盖MySQL各种特性的实践，优化案例，数据库架构，HA，监控等，有扫雷功效。 爱可生开源社区持续运营维护的小目标： 每周至少推送一篇高质量技术文章 每月研发团队发布开源组件新版 每年1024开源一款企业级组件 2019年至少25场社区活动 欢迎大家持续关注～ ...
mysql的GTID同步原理介绍及详细配置过程
最新发布
m0_58833554的博客
10-04 1869
介绍mysql的GTID主从同步原理以及详细配置过程
Mysql5.7 MGR集群搭建手册
04-22
在搭建MGR集群之前，需要做好环境准备，包括数据库服务器规划、安装mysql5.7.20以及设置hostname和ip映射。然后，需要创建复制环境，包括配置/etc/***f、开启二进制日志记录、设置binlog格式等。 以上就是对MGR集群...
万里数据库MGR Bug修复之路 - 娄帅
06-23
然而，即使是先进的技术也可能遇到问题，本文将探讨在MGR集群中发现并修复的一个具体Bug案例。 在介绍MGR架构之前，首先需要了解Group Replication Plugin Architecture的分层设计。MGR插件分为多个层次，包括...
MGRMySQL Group Replication学习笔记.pdf
07-23
1. **高一致性**：MGR通过原生复制和paxos协议来保障数据在集群中各个节点间的一致性。 2. **高容错性**：即便不是大多数节点出现问题，集群也能继续正常工作。当节点间发生资源争用冲突时，系统不会报错，而是按照...
mysql semi sync_MySQL semisync replication配置及源代码实现
weixin_39641257的博客
02-07 186
之前一直没有对semi sync做太多的关注，原因是线上的生产环境使用的非常少，最近需要提升semisync的生产环境优先级，以适应数据保护非常严格的场景，借此机会了解一下semisync，顺便过了一下大部分代码，以帮助后续的性能优化工作，以下分析基于代码MySQL5.6.13如何配置semisync的配置非常简单，采用MySQL Plugin的方式，在主库和备库上分别安装不同的插件，当然你也可以...
mgr未同步 mysql_详解MySQL双活同步复制四种解决方案
weixin_39760389的博客
12-18 466
对于数据实时同步，其核心是需要基于日志来实现，是可以实现准实时的数据同步，基于日志实现不会要求数据库本身在设计和实现中带来任何额外的约束。基于MySQL原生复制主主同步方案这是常见的方案，一般来说，中小型规模的时候，采用这种架构是最省事的。两个节点可以采用简单的双主模式，并且使用专线连接，在master_A节点发生故障后，应用连接快速切换到master_B节点，反之也亦然。有几个需要注意的地方，脑...
解决nvidia-docker 问题 nvidia-docker | Error: failed to run docker command
筑梦之路
08-14 3888
这个问题也是搞了好久才搞定，首先是换了新的主板，开机很慢，nvidia-docker 运行不了了 由于要使用docker进行深度学习的程序部署，所以必须要调用显卡GPU 网上搜了很久没找到该问题的解决办法 最终在自己的研究下终于解决 思路如下： 1.检查默认的显卡驱动是否禁用lsmod|grep nouveau 2.如果没有禁用默认的显卡驱动，将会与nVidia的显卡驱动...
总结Pyinstaller的坑及终极解决方法
热门推荐
shuoGG的专栏
07-06 5万+
一. 首先要有个稳定环境 下面是博主经测试的觉得坑比较少的环境搭配 Python3.4 + PyQt5.4 + Pyinstaller3.2.1 Python3.5 + PyQt5.8 + Pyinstaller3.2.1 二. Pyinstaller遇到坑没必要换打包工具 博主好几次用Pyinstaller遇到坑时都有考虑换工具如py2exe或cx-freeze之类的,...
Maven 编译命令错误之编译错误的解决
木小鱼的笔记
06-03 1万+
引言： 解决在Linux系统中，运行mvn命令碰到的一个编译问题，看看如何分析并加以解决的？
线程一1.0 线程 获取线程的运行时异常，Hook线程
insis_mo的博客
03-19 273
下图： 线程在执行单元中是不允许抛出checked异常的，，而且线程运行在自己的上下文中，派生他的线程将无法直接获得它运行中出现的异常信息，对此Java给我们提供了一个uncaughtexceptionHandler接口，当线程在运行过程中出现异常时，就会回调UncaughtExceptionHandler接口，从而得知那个线程在运行中出错，以及出现了什么样的错误，如下 public st...
MySQL半同步复制--RUN_HOOK
帅的数说
09-03 1993
半同步复制只是一个插件，一个动态加载的插件怎么实现事务处理线程等待、停下来呢？ 这个插件只是个实现体，在MySQL源码中还是需要支撑这个实现体的框架。即在代码的某些位置，加入一些桩observer，在执行到这些桩的时候，如果有插件在这些observer中注册了实现体，就这执行这些实现体，否则什么也不执行。 RUN_HOOK就是这些桩的调用接口： #define RUN_HOOK(grou
一周碎碎念，2021.11.7，两个MGR集群间还可以构建传统的主从复制通道吗
老叶茶馆
11-07 413
叨叨最近遇到的一些事以及见闻、思考。1. GreatSQL编译环境Dockerfile更新了用于构建GreatSQL编译环境的Dockerfile发现几个小瑕疵，于是更新了下。利用Dock...
MySQL 8.0 MGR集群自动安装与配置教程
- 接下来修改MySQL配置文件，设置组复制的相关参数，如server_id、binlog_format、gtid_executed等。 - 配置好MySQL的server_uuid，这是在组复制中唯一标识每个服务器的标识符。 - 最后启动所有MySQL实例，并初始化...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值