MGR8.0需求与限制

一、需求：

a.体系结构

1.innodb storage engine ，必段是innodb 事务引擎

2.primary key，每个表必须定主键或非空唯一性键

3.ipv4 ,目前只支持ipv4

4.network performance,集群中服务器彼此非常近，网络性影响很重要

 

b.实例配置

1.binary log active , --log-bin[=log_file_name]

2.Slave Updates Logged, --log-slave-updates

3.Binary Log Row Format,--binlog-format=row

4.Global Transaction Identifiers On. --gtid-mode=ON

5.Replication Information Repositories.

--master-info-repository=TABLE

--relaylog-info-repository=TABLE

6.Transaction Write Set Extraction

--transaction-write-set-extraction=XXHASH64

用于侦查冲突

7.Multithreaded Appliers.

slave_preserve_commit_order=1

slave_parallel_workers

slave_parallel_type=LOGICAL_CLOCK

 

二、限制

1. Replication Event Checksums

--binlog-checksum=NONE

2. Gap Locks

READ COMMITTED

3.Table Locks and Named Locks.

The certification process does not take into account table

locks (see Section 13.3.6, “LOCK TABLES and UNLOCK TABLES Syntax”) or named locks (see GET_LOCK()).

4.SERIALIZABLE Isolation Level

5.Concurrent DDL versus DML Operations

6.Foreign Keys with Cascading Constraints

group_replication_single_primary_mode=OFF

group_replication_enforce_update_everywhere_checks=ON

7.Very Large Transactions.

8.Multi-primary Mode Deadlock

SELECT .. FOR UPDATE statements can result in a deadlock. This is because the lock is not shared across the members of the group, therefore the expectation for such a statement might not be reached.

9.Replication Filters

Global replication filters cannot be used on a MySQL server instance that

is configured for Group Replication, because filtering transactions on some servers would make the group unable to reach agreement on a consistent state