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/replication-asynchronous-connection-failover.html
However, you can delete a managed group manually if it is no longer needed. This feature works with Group Replication, on a group configured in single-primary mode, where the group’s primary is a replica that has a replication channel using the ...
https://dev.mysql.com/doc/refman/8.0/en/replication-bugs.html
In this case, the replication thread stops and waits for you to clean up the tables manually to bring them into synchrony. When you have determined that there is no user error involved, and replication still either does not work at all or is ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-flush.html
This is not normally a problem because these statements do not modify table data. In addition, if you use FLUSH TABLES when renaming a MyISAM table that is part of a MERGE table, you must issue FLUSH TABLES manually on the replicas. Some forms of ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-invoked.html
For example, trying to replicate a loadable function with statement-based replication generates this warning because it currently cannot be determined by the MySQL server whether the function is deterministic. In the case of CREATE EVENT and ALTER ... Replication of invoked features such as loadable functions and stored programs (stored procedures and functions, triggers, and events) provides the following characteristics: The effects of the feature are always ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-repair-table.html
However, any such modifications of table data performed by this statement are not replicated, which can cause source and replica to lose synchronization. When used on a corrupted or otherwise damaged table, it is possible for the REPAIR TABLE ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features.html
If you are planning to use statement-based replication between MySQL 8.0 and a previous MySQL release series, it is a good idea to consult the edition of the MySQL Reference Manual corresponding to the earlier release series for information ... The ...
https://dev.mysql.com/doc/refman/8.0/en/replication-howto-masterstatus.html
Warning This procedure uses FLUSH TABLES WITH READ LOCK, which blocks COMMIT operations for InnoDB tables. If you are planning to shut down the source to create a data snapshot, you can optionally skip this procedure and instead store a copy of the ... To configure the replica to start the replication process at the correct point, you need to note the source's current coordinates within its binary ...
https://dev.mysql.com/doc/refman/8.0/en/replication-mode-change-online-disable-gtids.html
This section describes how to disable GTID transactions on servers that are already online. This procedure does not require taking the server offline and is suited to use in production. You cannot disable GTID transactions online on any single ...
https://dev.mysql.com/doc/refman/8.0/en/replication-multi-source-provision-replica.html
This statement transfers the GTIDs for the transactions executed on the source to the replica, and the replica requires this information. In a multi-source replication topology, you must therefore remove the SET @@GLOBAL.gtid_purged statement from ... If the sources in the multi-source replication topology have existing data, it can save time to provision the replica with the relevant data before starting ...
https://dev.mysql.com/doc/refman/8.0/en/replication-privilege-checks-recover.html
Follow this procedure to recover from the error: Identify the replicated event that caused the error and verify whether or not the event is expected and from a trusted source. For instructions to do this, see Section 9.5, “Point-in-Time ... If a ...