Search Results
https://dev.mysql.com/doc/refman/8.4/en/group-replication-cloning.html
Be aware that a remote cloning operation removes user-created tablespaces and data from the joining member before transferring the data from the donor. Cloning is therefore not suitable for groups where members run different minor MySQL Server ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-deploying-locally.html
The instructions in this section are not suitable for production deployments because all MySQL server instances are running on the same single host. mysql-8.4/bin/mysqld --initialize-insecure --basedir=$PWD/mysql-8.4 --datadir=$PWD/data/s1 ... The ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-distributed-recovery-connections.html
The host name that the server is using for SQL client connections can be verified in the Member_host column of the Performance Schema table replication_group_members. The steps for a joining member to establish a connection for distributed recovery ... When a joining member connects to an online existing member for state transfer during distributed recovery, the joining member acts as a client on the connection and the existing member acts as a ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-distributed-recovery-fault.html
The donor for distributed recovery is selected randomly from the existing list of suitable online group members in the current view. When the member joining has restarted at the end of the operation, it establishes a connection with a new donor for ... 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 ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-failure-detection.html
If a member does not receive messages from another member for 5 seconds, it suspects that the member has failed, and lists the status of that member as UNREACHABLE in its own Performance Schema table replication_group_members. Where the network is ... Group Replication’s failure detection mechanism is a distributed service which is able to identify that a server in the group is not communicating with the others, and is therefore suspected of being out of ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-fault-tolerance.html
MySQL Group Replication builds on an implementation of the Paxos distributed algorithm to provide distributed coordination between servers. As such, it requires a majority of servers to be active to reach quorum and thus make a decision. This has ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-frequently-asked-questions.html
This limit has been identified from testing and benchmarking as a safe boundary where the group performs reliably on a stable local area network. And you can likely scale-out a small fraction of your IO operations, since remote servers receive only ...What is the maximum number of MySQL servers in a group? A group can consist of maximum 9 ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-functions.html
The functions described in the following sections are used with Group Replication.
https://dev.mysql.com/doc/refman/8.4/en/group-replication-multi-primary-mode.html
If a transaction executes against a table that has foreign keys with cascading constraints, then its commit fails when synchronizing itself with the group. In multi-primary mode (group_replication_single_primary_mode=OFF) no member has a special ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-options.html
The next two sections contain information about MySQL server system and server status variables which are specific to the Group Replication plugin.