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/gone-away.html
This section also covers the related Lost connection to server during query error. The most common reason for the MySQL server has gone away error is that the server timed out and closed the connection. In this case, you normally get one of the ...
https://dev.mysql.com/doc/refman/8.0/en/group-by-modifiers.html
The GROUP BY clause permits a WITH ROLLUP modifier that causes summary output to include extra rows that represent higher-level (that is, super-aggregate) summary operations. ROLLUP thus enables you to answer questions at multiple levels of ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication-background.html
The most common way to create a fault-tolerant system is to resort to making components redundant, in other words the component can be removed and the system should continue to operate as expected. This creates a set of challenges that raise ...
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-distributed-recovery.html
Whenever a member joins or rejoins a replication group, it must catch up with the transactions that were applied by the group members before it joined, or while it was away. The joining member begins by checking the relay log for its ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication-gtids.html
Group Replication uses GTIDs (global transaction identifiers) to track exactly which transactions have been committed on every server instance. The settings gtid_mode=ON and enforce_gtid_consistency=ON are required on all group members. Incoming ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication-online-upgrade-combining-versions.html
Group Replication is versioned according to the MySQL Server version that the Group Replication plugin was bundled with. For example, if a member is running MySQL 5.7.26 then that is the version of the Group Replication plugin. For optimal ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication-online-upgrade-considerations.html
When upgrading an online group you should consider the following points: Regardless of the way which you upgrade your group, it is important to disable any writes to group members until they are ready to rejoin the group. When a member is stopped, ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication-replication-group-members.html
The performance_schema.replication_group_members table is used for monitoring the status of the different server instances that are members of the group. The information in the table is updated whenever there is a view change, for example when the ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication-responses-failure.html
Group Replication's failure detection mechanism is designed to identify group members that are no longer communicating with the group, and expel them as and when it seems likely that they have failed. Having a failure detection mechanism increases ...