PDF (US Ltr)
- 43.2Mb
PDF (A4)
- 43.3Mb
Man Pages (TGZ)
- 295.2Kb
Man Pages (Zip)
- 400.3Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/group-replication-limitations.html
In order for a replication group to use fragmentation, all group members must be at MySQL 8.0.16 or above, and the Group Replication communication protocol version in use by the group must allow fragmentation. Limit on Group Size Limits on ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication-message-compression.html
However, it is advisable to set the same value on all group members in order to avoid unnecessary rollback of transactions, failure of message delivery, or failure of message recovery. For messages sent between online group members, Group ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication-network-partitioning.html
group_replication_force_members must be empty in order to issue a START GROUP_REPLICATION statement. The group needs to achieve consensus whenever a change that needs to be replicated happens. This is the case for regular transactions but is also ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication-offline-upgrade.html
In a multi-primary group you can shutdown the members in any order. To perform an offline upgrade of a Group Replication group, you remove each member from the group, perform an upgrade of the member and then restart the group as usual. In a ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication-online-upgrade-combining-versions.html
However, while you are in the process of upgrading an online group, in order to maximize availability, you might need to have members with different MySQL Server versions running at the same time. Group Replication is versioned according to the ...
https://dev.mysql.com/doc/refman/8.0/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.0/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.0/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.0/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.0/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, ...