PDF (US Ltr)
- 43.3Mb
PDF (A4)
- 43.4Mb
Man Pages (TGZ)
- 297.2Kb
Man Pages (Zip)
- 402.4Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/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.0/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.0/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.0/en/group-replication-functions-for-new-primary.html
You can identify the current primary using the MEMBER_ROLE column in the Performance Schema table replication_group_members, or the group_replication_primary_member status variable. The following function enables you to set a member of a ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication-functions.html
The functions described in the following sections are used with Group Replication.
https://dev.mysql.com/doc/refman/8.0/en/group-replication-multi-primary-mode.html
Figure 20.5, “Client Failover” shows how clients can reconnect to an alternative group member if a member leaves the group. If a transaction executes against a table that has foreign keys with cascading constraints, then its commit fails when ...
https://dev.mysql.com/doc/refman/8.0/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.
https://dev.mysql.com/doc/refman/8.0/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. On a ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication-single-primary-mode.html
20.1.3.1.1 Primary Election Algorithm The automatic primary member election process involves each member looking at the new view of the group, ordering the potential new primary members, and choosing the member that qualifies as the most suitable.
https://dev.mysql.com/doc/refman/8.0/en/group-replication-upgrading-member.html
Before proceeding, ensure that the member's status is OFFLINE by monitoring the replication_group_members table. This section explains the steps required for upgrading a member of a group. This procedure is part of the methods described at Section ...