Please enable JavaScript.
Coggle requires JavaScript to display documents.
MGR (test (requirements (exclusively use of InnoDB tables only, every…
MGR
test
-
-
limitations
-
-
SERIALIZABLE Isolation Level. SERIALIZABLE isolation level is not supported in multi-primary groups by default. Setting a transaction isolation level to SERIALIZABLE configures Group Replication to refuse to commit the transaction.
an object cannot be changed concurrently at different servers by two operations, where one of them is a DDL and the other is either a DML or DDL.
attentions
Large transactions are more vulnerable because:
Large write set may increase the likelihood of certification conflicts
Transaction taking longer to execute may be more vulnerable to be aborted by a certified transaction.
Small transactions changing a very small set of data (hotspots):
Concurrently executing them at different sites will trade-off contention with roll backs due to the optimistic execution
-
-
-
-
-
-
-
pre-production
-
LOCK
Gap Locks. The certification process does not take into account gap locks, as information about gap locks is not available outside of InnoDB. See Gap Locks for more information.
Table Locks and Named Locks. The certification process does not take into account table locks (see Section 14.3.5, “LOCK TABLES and UNLOCK TABLES Syntax”) or named locks (see GET_LOCK()).
-
-
-
-
-
-
节点 crash 的处理
Once a server is removed from the group, you need to join it back again. In other words, after a server is removed explicitly from the group you need to rejoin it manually (or have a script doing it automatically).
concet
-
-
- A node (member of the group) send the changes (binlog events) made by a transaction to the group through the GCS.
- All members consume the writeset and certify it
- If passed it is applied, if failed, transaction is rolled back on originating server and discarded at other servers.
-
-
-
Group Replication now also takes full advantage of parallel binary log applier infrastructure
– Reduces applier lag and improves replication performance considerably
– Configured in the same way as in asynchronous replication
--slave_parallel_workers=NUMBER
--slave_parallel_type=logical_clock
--slave_preserve_commit_order=ON
-
-
