Search Results
https://dev.mysql.com/doc/refman/8.4/en/replication-features-functions.html
To avoid unexpected results when replicating between MySQL servers in different time zones, set the time zone on both source and replica. To explain the potential problems when replicating between servers which are in different time zones, suppose ... Certain functions do not replicate well under some conditions: The USER(), CURRENT_USER() (or CURRENT_USER), UUID(), VERSION(), and LOAD_FILE() functions are replicated without change and thus do not work reliably on the replica unless row-based replication is ...
https://dev.mysql.com/doc/refman/8.4/en/replication-features-temptables.html
In statement-based replication mode, CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE statements cannot be used inside a transaction, procedure, function, or trigger when GTIDs are in use on the server (that is, when the enforce_gtid_consistency ...
https://dev.mysql.com/doc/refman/8.4/en/replication-functions-synchronization.html
The functions listed in this section are used for controlling position-based synchronization of source and replica servers in MySQL Replication. The binary log file position can be marked as invalid when the CHANGE REPLICATION SOURCE TO option ...
https://dev.mysql.com/doc/refman/8.4/en/replication-privilege-checks-account.html
The REPLICATION_APPLIER privilege explicitly or implicitly allows the PRIVILEGE_CHECKS_USER account to carry out the following operations that a replication thread needs to perform: Setting the value of the system variables gtid_next, ... The user ...
https://dev.mysql.com/doc/refman/8.4/en/replication-semisync-monitoring.html
To check the current values of the status variables, use SHOW STATUS: mysql> SHOW STATUS LIKE 'Rpl_semi_sync%'; All Rpl_semi_sync_xxx status variables are described at Section 7.1.10, “Server Status Variables”. Some examples are: ... The plugins ...
https://dev.mysql.com/doc/refman/8.4/en/replication-solutions-backups.html
Another backup strategy, which can be used for either source or replica servers, is to put the server in a read-only state. The backup is performed against the read-only server, which then is changed back to its usual read/write operational status.
https://dev.mysql.com/doc/refman/8.4/en/replication-solutions-performance.html
Binary logging is enabled on both source servers, which is the default. Source 2 is the replica to the server Source 1 that provides the replication functionality to the remainder of the replicas in the replication structure. Setting a large value ... 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 ...
https://dev.mysql.com/doc/refman/8.4/en/replication-solutions-switch.html
In a failover situation, all the servers in the group are typically executing the same events from the same binary log file, so changing the source of the events should not affect the structure or integrity of the database, provided that you ... You ...
https://dev.mysql.com/doc/refman/8.4/en/reproducible-test-case.html
If you want to find a statement that crashes mysqld, you should start the server with the general query log enabled as well. When you have gotten a crashed table, stop the mysqld server. For information about steps to take when encountering InnoDB ...
https://dev.mysql.com/doc/refman/8.4/en/reset-persist.html
Removing a persisted system variable causes the variable no longer to be initialized from mysqld-auto.cnf at server startup. On the other hand, because RESET PERSIST does not change variable values, it has no effect on the contents of the ... RESET ...