Search Results
https://dev.mysql.com/doc/refman/8.4/en/group-replication-online-upgrade-methods.html
If you do not mind which member is the primary, the members can be upgraded in any order. Choose one of the following methods of upgrading a Group Replication group: Rolling In-Group Upgrade This method is supported provided that servers running a ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-performance-xcom-cache-reduce.html
If a reconnecting member cannot retrieve all the messages it needs from the XCom message cache, the member must leave the group and rejoin it, in order to retrieve the missing transactions from another member's binary log using distributed recovery.
https://dev.mysql.com/doc/refman/8.4/en/group-replication-performance.html
If a group experiences a level of difficulties such that it cannot contact a majority of its members in order to agree on a decision, it identifies itself as having lost quorum and stops processing transactions. Group Replication is designed to ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-replication-group-member-stats.html
Based on this information, you could decide to either remove the member from the group, or delay the processing of transactions on the other members of the group in order to reduce the number of queued transactions. Each member in a replication ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-responses-failure-exit.html
In order of impact, the exit actions are as follows: If READ_ONLY is the exit action, the instance switches MySQL to super read only mode by setting the system variable super_read_only to ON. The group_replication_exit_state_action system variable ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-responses-failure-expel.html
It is not mandatory for all members of a group to have the same setting for group_replication_member_expel_timeout, but it is recommended in order to avoid unexpected expulsions. You can use the group_replication_member_expel_timeout system ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-throttling.html
In order to avoid large jumps in throughput once the queue size goes beyond the threshold, the throughput is only allowed to grow by the same 10% per period after that. Based on the metrics gathered across all servers in the group, a throttling ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-understanding-consistency-guarantees.html
Group Replication uses a total order on writes, and therefore this implies waiting for this and all preceding writes that are in secondaries’ queues to be applied. In terms of distributed consistency guarantees, either in normal or failure repair ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-upgrading-member.html
The recommended order of upgrading members in a single-primary group is to upgrade all secondaries, and then upgrade the primary last. This section explains the steps required for upgrading a member of a group. This procedure is part of the methods ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-user-credentials.html
Group Replication uses a distributed recovery process to synchronize group members when joining them to the group. Distributed recovery involves transferring transactions from a donor's binary log to a joining member using a replication channel ...