PDF (US Ltr)
- 43.3Mb
PDF (A4)
- 43.4Mb
Man Pages (TGZ)
- 297.2Kb
Man Pages (Zip)
- 402.4Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/replication-features-max-allowed-packet.html
The value of replica_pending_jobs_size_max or slave_pending_jobs_size_max is a soft limit, and if an unusually large event (consisting of one or multiple packets) exceeds this size, the transaction is held until all the replica workers have empty ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-memory.html
The safe way to restart a replica that is replicating MEMORY tables is to first drop or delete all rows from the MEMORY tables on the source and wait until those changes have replicated to the replica. When a replication source server shuts down ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-row-searches.html
When all the records in the target table have been checked, the algorithm verifies whether the hash table is now empty. When a replica using row-based replication format applies an UPDATE or DELETE operation, it must search the relevant table for ...
https://dev.mysql.com/doc/refman/8.0/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.0/en/replication-formats.html
The statement-based and row-based replication formats have different issues and limitations. Replication works because events written to the binary log are read from the source and then processed on the replica. The events are recorded within the ...
https://dev.mysql.com/doc/refman/8.0/en/replication-functions.html
MASTER_POS_WAIT() Block until the replica has read and applied all updates up to the specified position 8.0.26 SOURCE_POS_WAIT() Block until the replica has read and applied all updates up to the specified position 8.0.26 ... The functions described ...
https://dev.mysql.com/doc/refman/8.0/en/replication-gtids.html
This section explains transaction-based replication using global transaction identifiers (GTIDs). Because GTID-based replication is completely transaction-based, it is simple to determine whether sources and replicas are consistent; as long as all ...
https://dev.mysql.com/doc/refman/8.0/en/replication-howto-masterbaseconfig.html
Note The following options also have an impact on the source: For the greatest possible durability and consistency in a replication setup using InnoDB with transactions, you should use innodb_flush_log_at_trx_commit=1 and sync_binlog=1 in the ... To ...
https://dev.mysql.com/doc/refman/8.0/en/replication-howto-repuser.html
Although you do not have to create an account specifically for replication, you should be aware that the replication user name and password are stored in plain text in the replica's connection metadata repository mysql.slave_master_info (see Section ... Each replica connects to the source using a MySQL user name and password, so there must be a user account on the source that the replica can use to ...
https://dev.mysql.com/doc/refman/8.0/en/replication-mode-change-online.html
This section describes how to change the mode of replication from and to GTID mode without having to take the server offline.