Search Results
https://dev.mysql.com/doc/refman/8.4/en/group-replication-flow-control.html
MySQL Group Replication ensures that a transaction commits only after a majority of the members in a group have received it and agreed on the relative order amongst all transactions sent concurrently. This approach works well if the total number of ...If it does, and some members have less write throughput than others—particularly less than the writer members—these members may start lagging behind the ...
https://dev.mysql.com/doc/mysql-shell/9.4/en/shell-admin-api-communication-stack.html
InnoDB Cluster and ClusterSet support the MySQL communication stack introduced for Group Replication in MySQL 8.0.27. The new option, communicationStack: XCOM|MYSQL sets the value of the Group Replication system variable ...Note It is not possible ...
https://dev.mysql.com/doc/refman/8.4/en/start-group-replication.html
START GROUP_REPLICATION [USER='user_name'] [, PASSWORD='user_pass'] [, DEFAULT_AUTH='plugin_name'] Starts group replication. This statement requires the GROUP_REPLICATION_ADMIN privilege (or the deprecated SUPER privilege). If super_read_only=ON is ...For instructions to set up this account, see Section 20.2.1.3, “User Credentials For Distributed ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-performance-xcom-cache.html
The group communication engine for Group Replication (XCom, a Paxos variant) includes a cache for messages (and their metadata) exchanged between the group members as a part of the consensus protocol. Among other functions, the message cache is ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-responses-failure-rejoin.html
The group_replication_autorejoin_tries system variable makes a member that has been expelled or reached its unreachable majority timeout try to rejoin the group automatically. The default (3), means that the member automatically makes 3 attempts to ...Using the auto-rejoin feature is appropriate if you can tolerate the possibility of stale reads and want to minimize the need for manual intervention, especially where transient network issues fairly often result in the expulsion of ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-consistency-guarantees.html
One of the major implications of a distributed system such as Group Replication is the consistency guarantees that it provides as a group. In other words, the consistency of the global synchronization of transactions distributed across the members ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-distributed-recovery-securing.html
Important When using the MySQL communication stack (group_replication_communication_stack=MYSQL) AND secure connections between members (group_replication_ssl_mode is not set to DISABLED), the security settings discussed in this section are applied ...For a full description of distributed recovery, see Section 20.5.4, “Distributed ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-observability.html
There is a lot of automation built into the Group Replication plugin. This is where the instrumentation of Group Replication and Performance Schema becomes important. The distributed nature of the replication protocol and the fact that server ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-performance-xcom-cache-increase.html
If a member is absent for a period that is not long enough for it to be expelled from the group, it can reconnect and start participating in the group again by retrieving missed transactions from another member's XCom message cache. Group ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-performance-xcom-cache-reduce.html
Having a very low group_replication_message_cache_size setting is not recommended if the host is on an unstable network, because a smaller message cache makes it harder for group members to reconnect after a transient loss of connectivity. If a ...