PDF (US Ltr)
- 35.0Mb
PDF (A4)
- 35.1Mb
Man Pages (TGZ)
- 254.9Kb
Man Pages (Zip)
- 359.9Kb
Info (Gzip)
- 3.4Mb
Info (Zip)
- 3.4Mb
Search Results
https://dev.mysql.com/doc/refman/5.7/en/replication-bugs.html
For example, if you update the replica outside of the replication thread, the data goes out of synchrony, and you can have unique key violations on updates. When you have determined that there is no user error involved, and replication still either ...
https://dev.mysql.com/doc/refman/5.7/en/replication-gtids-concepts.html
A global transaction identifier (GTID) is a unique identifier created and associated with each transaction committed on the server of origin (the source). This identifier is unique not only to the server on which it originated, but is unique across ...
https://dev.mysql.com/doc/refman/5.7/en/replication-gtids-failover.html
GTIDs play a key role in applying changes to the database: the server automatically skips any transaction having an identifier which the server recognizes as one that it has processed before. There are a number of techniques when using MySQL ...
https://dev.mysql.com/doc/refman/5.7/en/replication-gtids-howto.html
The key steps in this startup process for the simplest possible GTID replication topology, consisting of one source and one replica, are as follows: If replication is already running, synchronize both servers by making them read-only. This section ...
https://dev.mysql.com/doc/refman/5.7/en/replication-mode-change-online-concepts.html
To be able to safely configure the replication mode of an online server it is important to understand some key concepts of replication. This section explains these concepts and is essential reading before attempting to modify the replication mode ...
https://dev.mysql.com/doc/refman/5.7/en/replication-multi-source-monitoring.html
This enables you to write complex queries based on Channel_Name as a key. To monitor the status of replication channels the following options exist: Using the replication Performance Schema tables. By default, if the FOR CHANNEL channel clause is ...
https://dev.mysql.com/doc/refman/5.7/en/replication-options-reference.html
slave_exec_mode: Allows for switching replication thread between IDEMPOTENT mode (key and some other errors suppressed) and STRICT mode; STRICT mode is default, except for NDB Cluster, where IDEMPOTENT is always used. The following two sections ...
https://dev.mysql.com/doc/refman/5.7/en/replication-sbr-rbr.html
SELECT INSERT statements with AUTO_INCREMENT UPDATE or DELETE statements with WHERE clauses that do not use keys or do not change most of the examined rows. For most users, the mixed replication format should provide the best combination of data ...
https://dev.mysql.com/doc/refman/5.7/en/replication-solutions-unexpected-replica-halt.html
The innodb_flush_log_at_trx_commit=1 setting mentioned in the list below is a key setting for a replication setup that uses InnoDB with transactions. In order for replication to be resilient to unexpected halts of the server (sometimes described as ...
https://dev.mysql.com/doc/refman/5.7/en/reset-master.html
RESET MASTER Warning Use this statement with caution to ensure you do not lose any wanted binary log file data and GTID execution history. For a server where binary logging is enabled (log_bin is ON), RESET MASTER deletes all existing binary log ...