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-network-partitioning.html
Check replication_group_members on both s1 and s2 to verify the group membership after this change. 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-observability.html
For example, you can connect to a single server in the group and obtain both local and global information by issuing select statements on the Group Replication related Performance Schema tables. There is a lot of automation built into the Group ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication-online-upgrade-methods.html
This assumes that you have enough servers to run both groups simultaneously. 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 newer version ...
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-probes-and-statistics.html
The information is shared every second, and this period is sufficient to address both concerns. The monitoring mechanism works by having each member deploying a set of probes to collect information about its work queues and throughput. It then ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication-requirements.html
The performance and stability of a group can be impacted by both network latency and network bandwidth. Infrastructure Server Instance Configuration Server instances that you want to use for Group Replication must satisfy the following requirements. Transactions are executed optimistically and then, at commit time, are checked for ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication-responses-failure-exit.html
This exit action prevents both updates and stale reads (with the exception of reads by client users with the stated privileges), and enables proxy tools such as MySQL Router to recognize that the server is unavailable and redirect client connections. The group_replication_exit_state_action system variable, which is available from MySQL 8.0.12 and MySQL 5.7.24, specifies what Group Replication does when the member leaves the group unintentionally due to an error or problem, and either fails to auto-rejoin or does not ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication-responses-failure.html
In this situation, the default behavior is for the members in both the minority and the majority to remain in the group, continue to accept transactions (although they are blocked on the members in the minority), and wait for operator intervention.
https://dev.mysql.com/doc/refman/8.0/en/group-replication-secure-socket-layer-support-ssl.html
Each member's connections to other existing members continue to use the highest available protocol that both members support. Secure sockets can be used for group communication connections between members of a group. The Group Replication system ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication-secure-user.html
State transfer from the binary log requires a replication user with the correct permissions so that Group Replication can establish direct member-to-member replication channels. The same replication user is used for distributed recovery on all the ...