PDF (US Ltr)
- 43.2Mb
PDF (A4)
- 43.3Mb
Man Pages (TGZ)
- 295.2Kb
Man Pages (Zip)
- 400.4Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/group-replication-configuring-instances.html
Set the disabled_storage_engines system variable as follows to prevent their use: disabled_storage_engines="MyISAM,BLACKHOLE,FEDERATED,ARCHIVE,MEMORY" Note that with the MyISAM storage engine disabled, when you are upgrading a MySQL instance to a ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication-deploying-locally.html
Note The non-default port of 24801 is used because in this tutorial the three server instances use the same hostname. The most common way to deploy Group Replication is using multiple server instances, to provide high availability. It is also ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication-functions-for-member-actions.html
Note that if there is more than one channel with SOURCE_CONNECTION_AUTO_FAILOVER=1, the member action covers all the channels, so they cannot be individually enabled and disabled by this method. The following functions can be used to enable and ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication-group-membership.html
In MySQL Group Replication, a set of servers forms a replication group. A group has a name, which takes the form of a UUID. The group is dynamic and servers can leave (either voluntarily or involuntarily) and join it at any time. If a server joins ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication-gtids.html
These options are normally set using a CHANGE REPLICATION SOURCE TO statement, but note that you cannot disable them for a Group Replication channel. Group Replication uses GTIDs (global transaction identifiers) to track exactly which transactions ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication-message-compression.html
Note that the maximum supported input size for the LZ4 compression algorithm is 2113929216 bytes. For messages sent between online group members, Group Replication enables message compression by default. Whether a specific message is compressed ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication-monitoring.html
Note If you are monitoring one or more secondary instances using mysqladmin, you should be aware that a FLUSH STATUS statement executed by this utility creates a GTID event on the local instance which may impact future group operations. You can use ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication-network-partitioning.html
Note Loss of quorum is by itself a side-effect of bad planning. 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 required for group membership changes ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication-online-upgrade-combining-versions.html
Note that joining members running releases before MySQL 5.7.27 check against all group members to find whether their own MySQL Server major version is lower. Group Replication is versioned according to the MySQL Server version that the Group ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication-replication-group-member-stats.html
Note that refreshing of statistics for remote members is controlled by the message period specified in the group_replication_flow_control_period option, so these can differ slightly from the locally collected statistics for the member where the ...