Search Results
https://dev.mysql.com/doc/refman/8.4/en/group-replication-deploying-locally.html
The most common way to deploy Group Replication is using multiple server instances, to provide high availability. It is also possible to deploy Group Replication locally, for example for testing purposes. Important Group Replication is usually ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-distributed-recovery-fault.html
Group Replication's distributed recovery process has a number of built-in measures to ensure fault tolerance in the event of any problems during the process. The donor for distributed recovery is selected randomly from the existing list of suitable ...
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 ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-functions-for-communication-protocol.html
The following functions enable you to inspect and configure the Group Replication communication protocol version that is used by a replication group. Section 20.7.4, “Message Compression” Section 20.7.5, “Message Fragmentation” Section ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-functions-for-maximum-consensus.html
The following functions enable you to inspect and configure the maximum number of consensus instances that a group can execute in parallel. group_replication_get_write_concurrency() Check the maximum number of consensus instances that a group can ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-functions-for-mode.html
The following functions enable you to control the mode which a replication group is running in, either single-primary or multi-primary mode. group_replication_switch_to_multi_primary_mode() Changes a group running in single-primary mode to ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-gtids.html
Group Replication uses GTIDs (global transaction identifiers) to track exactly which transactions have been committed on every server instance. The settings gtid_mode=ON and enforce_gtid_consistency=ON are required on all group members. Incoming ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-replication-group-members.html
The performance_schema.replication_group_members table is used for monitoring the status of the different server instances that are members of the group. The information in the table is updated whenever there is a view change, for example when the ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-responses-failure.html
Group Replication's failure detection mechanism is designed to identify group members that are no longer communicating with the group, and expel them as and when it seems likely that they have failed. Having a failure detection mechanism increases ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-upgrade-with-mysqlbackup.html
As part of a provisioning approach you can use MySQL Enterprise Backup to copy and restore the data from a group member to new members. However you cannot use this technique to directly restore a backup taken from a member running an older version ...