Search Results
https://dev.mysql.com/doc/refman/8.4/en/replication-features-reserved-words.html
You can encounter problems when you attempt to replicate from an older source to a newer replica and you make use of identifiers on the source that are reserved words in the newer MySQL version running on the replica. For example, a table column ...
https://dev.mysql.com/doc/refman/8.4/en/replication-features-shutdowns.html
It is safe to shut down a replication source server and restart it later. When a replica loses its connection to the source, the replica tries to reconnect immediately and retries periodically if that fails. This may be changed with the CHANGE ...
https://dev.mysql.com/doc/refman/8.4/en/replication-features-temptables.html
In MySQL 8.4, when binlog_format is set to ROW or MIXED, statements that exclusively use temporary tables are not logged on the source, and therefore the temporary tables are not replicated. Statements that involve a mix of temporary and ...
https://dev.mysql.com/doc/refman/8.4/en/replication-features-timezone.html
By default, source and replica servers assume that they are in the same time zone. If you are replicating between servers in different time zones, the time zone must be set on both source and replica. Otherwise, statements depending on the local ...
https://dev.mysql.com/doc/refman/8.4/en/replication-multi-source-adding-binlog-master.html
These steps assume that binary logging is enabled on the source (which is the default), the replica is using TABLE based replication applier metadata repositories (which is the default in MySQL 8.4), and that you have enabled a replication user and ...
https://dev.mysql.com/doc/refman/8.4/en/replication-multi-source-monitoring.html
To monitor the status of replication channels the following options exist: Using the replication Performance Schema tables. This enables you to write complex queries based on Channel_Name as a key. By default, if the FOR CHANNEL channel clause is ...
https://dev.mysql.com/doc/refman/8.4/en/replication-multi-source.html
Multi-source replication in MySQL 8.4 enables a replica to receive transactions from multiple immediate sources in parallel. In a multi-source replication topology, a replica creates a replication channel for each source that it should receive ...
https://dev.mysql.com/doc/refman/8.4/en/replication-privilege-checks-recover.html
If a privilege check against the PRIVILEGE_CHECKS_USER account fails, the transaction is not executed and replication stops for the channel. Details of the error and the last applied transaction are recorded in the Performance Schema ...
https://dev.mysql.com/doc/refman/8.4/en/replication-solutions-performance.html
As the number of replicas connecting to a source increases, the load, although minimal, also increases, as each replica uses a client connection to the source. Also, as each replica must receive a full copy of the source's binary log, the network ...
https://dev.mysql.com/doc/refman/8.4/en/replication-solutions-rbr-monitoring.html
The current progress of the replication applier (SQL) thread when using row-based replication is monitored through Performance Schema instrument stages, enabling you to track the processing of operations and check the amount of work completed and ...