https://dev.mysql.com/replication-features-sql-mode.html
Using different server SQL mode settings on the master and the slave may cause the same INSERT statements to be handled differently on the master and the slave, leading the master and slave to diverge. For best results, you should always use the ...
https://dev.mysql.com/replication-features-transactions.html
That is, such transactions can lead to master storage engine-specific behavior with the possible effect of replication going out of synchrony. In general, you should avoid transactions that update both transactional and nontransactional tables in a ...
https://dev.mysql.com/replication-features-triggers.html
If under row-based replication the slave applied the triggers as well as the row changes caused by them, the changes would in effect be applied twice on the slave, leading to different data on the master and the slave. With statement-based ...
https://dev.mysql.com/replication-features-variables.html
sql_mode is also replicated except for the NO_DIR_IN_CREATE mode; the slave always preserves its own value for NO_DIR_IN_CREATE, regardless of changes to it on the master. However, when mysqlbinlog parses a SET @@sql_mode = mode statement, the full ...
https://dev.mysql.com/replication-gtids-auto-positioning.html
The master and slave can diverge if any clients commit transactions on the master after it is restarted, which can lead to the situation where the master and slave are using the same GTID for different transactions. GTIDs replace the file-offset ...
https://dev.mysql.com/replication-rbr-safe-unsafe.html
If a large number of such statements were executed on the master, this could lead to excessively large error log files. The “safeness” of a statement in MySQL replication refers to whether the statement and its effects can be replicated ...
https://dev.mysql.com/replication-rules-examples.html
This can sometimes lead to results that seem counterintuitive, and that may be different depending on whether you are using statement-based or row-based replication; see the text for an example. This section provides additional explanation and ...
https://dev.mysql.com/replication-solutions.html
See Section 17.3.6, “Replicating Different Databases to Different Slaves” As the number of replication slaves increases, the load on the master can increase and lead to reduced performance (because of the need to replicate the binary log to each ... Replication can be used in many different environments for a range of ...
https://dev.mysql.com/resignal.html
RESIGNAL may change some or all information before passing it on. RESIGNAL is related to SIGNAL, but instead of originating a condition as SIGNAL does, RESIGNAL relays existing condition information, possibly after modifying it. RESIGNAL makes it ...
https://dev.mysql.com/show-slave-status.html
Any changes—including NTP updates—can lead to clock skews that can make calculation of Seconds_Behind_Master less reliable. SHOW SLAVE STATUS [FOR CHANNEL channel] This statement provides status information on essential parameters of the slave ...
