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-change-primary.html
This section explains how to change which member of a single-primary group is the primary, using the group_replication_set_as_primary() function, which can be can be run on any member of the group. When this is done, the current primary becomes a ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication-compatibility-upgrade.html
When all members have been upgraded to the same release, from MySQL 8.0.17, they all change back to read-write mode automatically. During an online upgrade procedure, if the group is in single-primary mode, all the servers that are not currently ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication-deploying-locally.html
Usually you want all members to be able to serve as seeds for members that are joining the group and have not got the transactions processed by the group. The remaining steps of Section 20.2.1, “Deploying Group Replication in Single-Primary ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication-functions-for-communication-protocol.html
You do not have to use these functions yourself for an InnoDB cluster. For an upgrade, specify the new MySQL Server version to which the existing group members have been upgraded. The following functions enable you to inspect and configure the ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication-offline-upgrade.html
If you have a requirement to allow members at earlier releases to join, you can use the group_replication_set_communication_protocol() function to downgrade the communication protocol version, specifying the MySQL Server version of the prospective ... 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 ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication-online-upgrade-methods.html
When all members have been upgraded to the same release, from MySQL 8.0.17, they all change back to read-write mode automatically. This assumes that you have enough servers to run both groups simultaneously. Choose one of the following methods of ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication-performance-message-fragmentation.html
For example: STOP GROUP_REPLICATION; SET GLOBAL group_replication_communication_max_message_size= 5242880; START GROUP_REPLICATION; Message delivery for a fragmented message is considered complete when all the fragments of the message have been ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication-performance-xcom-cache-reduce.html
If you reduce the cache size limit, XCom removes the oldest entries that have been decided and delivered until the current size is below the limit. The minimum setting for the XCom message cache size is 1 GB up to MySQL 8.0.20. From MySQL 8.0.21, ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication-responses-failure-expel.html
The waiting period before expelling a member only applies to members that have previously been active in the group. It is not mandatory for all members of a group to have the same setting for group_replication_member_expel_timeout, but it is ... You ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication-secure-user.html
If group members have been set up to support the use of a remote cloning operation as part of distributed recovery, which is available from MySQL 8.0.17, this replication user is also used as the clone user on the donor, and requires the correct ...