PDF (US Ltr)
- 35.1Mb
PDF (A4)
- 35.2Mb
Man Pages (TGZ)
- 256.4Kb
Man Pages (Zip)
- 361.2Kb
Info (Gzip)
- 3.4Mb
Info (Zip)
- 3.4Mb
Search Results
https://dev.mysql.com/doc/refman/5.7/en/replica-io-thread-states.html
Waiting to reconnect after a failed binlog dump request If the binary log dump request failed (due to disconnection), the thread goes into this state while it sleeps, then tries to reconnect periodically. The following list shows the most common ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-flush.html
If you replicate the privilege tables in the mysql database and update those tables directly without using GRANT, you must issue a FLUSH PRIVILEGES on the replicas to put the new privileges into effect. Some forms of the FLUSH statement are not ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-memory.html
When a replication source server shuts down and restarts, its MEMORY tables become empty. To replicate this effect to replicas, the first time that the source uses a given MEMORY table after startup, it logs an event that notifies replicas that the ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-sql-mode.html
It may also cause inserts into partitioned tables that succeed on the source to fail on the replica. Using different server SQL mode settings on the source and the replica may cause the same INSERT statements to be handled differently on the source ...
https://dev.mysql.com/doc/refman/5.7/en/replication-gtids-auto-positioning.html
If the issue is only missing transactions on the source, you can make the source into a replica instead, allow it to catch up with the other servers in the replication topology, and then make it a source again if needed. GTIDs replace the ...
https://dev.mysql.com/doc/refman/5.7/en/replication-gtids-restrictions.html
It is possible to import a dump made using mysqldump into a MySQL server running with GTID mode enabled, provided that there are no GTIDs in the target server's binary log. Because GTID-based replication is dependent on transactions, some features ...
https://dev.mysql.com/doc/refman/5.7/en/replication-howto-additionalslaves.html
Copy the contents of the existing replica's relay log index file into the new replica's relay log index file, making sure to overwrite any content already in the file. You can add another replica to an existing replication configuration without ...
https://dev.mysql.com/doc/refman/5.7/en/replication-multi-source-provision-replica.html
For example: sed '/GTID_PURGED/d' dumpM1.sql > dumpM1_nopurge.sql sed '/GTID_PURGED/d' dumpM2.sql > dumpM2_nopurge.sql Use the mysql client to import each edited dump file into the replica. If the sources in the multi-source replication topology ...
https://dev.mysql.com/doc/refman/5.7/en/replication-options-gtids.html
The MySQL Server system variables described in this section are used to monitor and control Global Transaction Identifiers (GTIDs). For additional information, see Section 16.1.3, “Replication with Global Transaction Identifiers”.
https://dev.mysql.com/doc/refman/5.7/en/replication-rbr-safe-unsafe.html
In addition, an INSERT into a table that has a composite primary key containing an AUTO_INCREMENT column that is not the first column of this composite key is unsafe. The “safeness” of a statement in MySQL Replication, refers to whether the ...