Search Results
https://dev.mysql.com/doc/refman/8.4/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.4/en/replication-features.html
If you are planning to use statement-based replication between MySQL 8.4 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.4/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.4/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 if this option is set ...
https://dev.mysql.com/doc/refman/8.4/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 the following provisioning example, we assume that the SET @@GLOBAL.gtid_purged statement cannot be left in ... 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.4/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 ...
https://dev.mysql.com/doc/refman/8.4/en/replication-problems.html
Many users have lost time by not doing this soon enough after encountering problems. This should never happen if you have taken a proper snapshot of the source, and never modified the data on the replica outside of the replication threads. If the ...
https://dev.mysql.com/doc/refman/8.4/en/replication-rules-channel-based-filters.html
This section explains how to work with replication filters when multiple replication channels exist, for example in a multi-source replication topology. This is because the server IDs of replicas must be unique in a replication topology. This ...
https://dev.mysql.com/doc/refman/8.4/en/replication-solutions-scaleout.html
Most websites fit into this category, where users are browsing the website, reading articles, posts, or viewing products. Replication in this situation enables you to distribute the reads over the replicas, while still enabling your web servers to ... You can use replication as a scale-out solution; that is, where you want to split up the load of database queries across multiple database servers, within some reasonable ...
https://dev.mysql.com/doc/refman/8.4/en/replication-solutions-unexpected-replica-halt.html
This section describes the impact of an unexpected halt of a replica during replication, and how to configure a replica for the best chance of recovery to continue replication. This repository is created by default as an InnoDB table named ... In ...