Search Results
https://dev.mysql.com/doc/refman/8.4/en/group-replication-gtids.html
The settings are made automatically on the Group Replication channels when they are created, or when a member server in a replication group is upgraded. Group Replication uses GTIDs (global transaction identifiers) to track exactly which ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-ip-address-permissions.html
These addresses, and the localhost IP address for IPv4 and IPv6 are used to create an automatic Group Replication allowlist. When and only when the XCom communication stack is used for establishing group communications ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-multi-primary-mode.html
While traffic is flowing, transactions can be externalized on some members before the others, especially if some members have less write throughput than others, creating the possibility of stale reads. In multi-primary mode ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-performance.html
Group Replication is designed to create fault-tolerant systems with built-in failure detection and automated recovery. If a member server instance leaves voluntarily or stops communicating with the group, the remaining members agree a ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-responses-failure-partition.html
Setting a timeout means you do not need to pro-actively monitor for servers that are in a minority group after a network partition, and you can avoid the possibility of creating a split-brain situation (with two versions of the group membership) due ... By default, members that find themselves in a minority due to a network partition do not automatically leave the ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-restarting-group.html
In that situation, to re-create the group, it must be started by bootstrapping as if it was being started for the first time. Group Replication is designed to ensure that the database service is continuously available, even if some of the servers ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-upgrade-with-mysqlbackup.html
Repeat this process to create a suitable number of new instances, for example to be able to handle a failover. 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.
https://dev.mysql.com/doc/refman/8.4/en/group-replication-use-cases.html
Group Replication enables you to create fault-tolerant systems with redundancy by replicating the system state to a set of servers. Even if some of the servers subsequently fail, as long it is not all or a majority, the system is still available.
https://dev.mysql.com/doc/refman/8.4/en/group-replication-view-changes.html
The randomly generated part is generated when the group is created, and remains unchanged while there is at least one member in the group. When Group Replication's distributed recovery process is carrying out state transfer from the binary log, to ...
https://dev.mysql.com/doc/refman/8.4/en/host-cache.html
The server handles entries in the host cache like this: When the first TCP client connection reaches the server from a given IP address, a new cache entry is created to record the client IP, host name, and client lookup validation flag. The MySQL ...