Search Results
https://dev.mysql.com/doc/refman/8.4/en/purge-binary-logs.html
PURGE BINARY LOGS TO and PURGE BINARY LOGS BEFORE both fail with an error when binary log files listed in the .index file had been removed from the system by some other means (such as using rm on Linux). (Bug #18199, Bug #18453) To handle such ...
https://dev.mysql.com/doc/refman/8.4/en/replication-asynchronous-connection-failover-replica.html
When the feature is active and correctly configured, if the primary that is replicating goes offline or into an error state, the new primary starts replication on the same channel when it is elected. When the mysql_start_failover_channels_if_primary ... Asynchronous connection failover for replicas is activated automatically for a replication channel on a Group Replication primary when you set SOURCE_CONNECTION_AUTO_FAILOVER=1 in the CHANGE REPLICATION SOURCE TO statement for the ...
https://dev.mysql.com/doc/refman/8.4/en/replication-binlog-encryption-key-rotation.html
If any of the first four steps of the binary log master key rotation process cannot be completed correctly, an error message is issued explaining the situation and the consequences for the encryption status of the binary log files and relay log ...
https://dev.mysql.com/doc/refman/8.4/en/replication-channels.html
The error codes and messages that are issued when multi-source replication is enabled specify the channel that generated the error. In MySQL multi-source replication, a replica opens multiple replication channels, one for each source server. The ...
https://dev.mysql.com/doc/refman/8.4/en/replication-features-memory.html
replica_exec_mode=IDEMPOTENT applies globally to all tables, so it may hide other replication errors in non-MEMORY tables. When a replication source server shuts down and restarts, its MEMORY tables become empty. To replicate this effect to ...
https://dev.mysql.com/doc/refman/8.4/en/replication-features-row-searches.html
If no matching record is found, it returns the error ER_KEY_NOT_FOUND and stops the replication applier thread. If there are any unmatched rows remaining in the hash table, the algorithm returns the error ER_KEY_NOT_FOUND and stops the replication ... When a replica using row-based replication format applies an UPDATE or DELETE operation, it must search the relevant table for the matching ...
https://dev.mysql.com/doc/refman/8.4/en/replication-multi-source-monitoring.html
The error codes and messages that are issued when multi-source replication is enabled specify the channel that generated the error. row *************************** CHANNEL_NAME: source_1 GROUP_NAME: SOURCE_UUID: 046e41f8-a223-11e4-a975-0811960cc264 ... To monitor the status of replication channels the following options exist: Using the replication Performance Schema ...
https://dev.mysql.com/doc/refman/8.4/en/replication-problems.html
If you have followed the instructions but your replication setup is not working, the first thing to do is check the error log for messages. If you cannot tell from the error log what the problem was, try the following techniques: Verify that the ...
https://dev.mysql.com/doc/refman/8.4/en/replication-rbr-usage.html
When replica_exec_mode is IDEMPOTENT, a failure to apply changes from RBL because the original row cannot be found does not trigger an error or cause replication to fail. MySQL uses statement-based logging (SBL), row-based logging (RBL) or ...
https://dev.mysql.com/doc/refman/8.4/en/replication-rules.html
Filtering rules are applied before performing any privilege checks; if a transaction is filtered out, no privilege check is performed for that transaction, and thus no error can be raised by it. If a replication source server does not write a ...