PDF (US Ltr)
- 41.8Mb
PDF (A4)
- 41.9Mb
Man Pages (TGZ)
- 272.3Kb
Man Pages (Zip)
- 378.3Kb
Info (Gzip)
- 4.2Mb
Info (Zip)
- 4.2Mb
Search Results
https://dev.mysql.com/doc/refman/9.7/en/replication-features-errors.html
If a statement produces the same error (identical error code) on both the source and the replica, the error is logged, but replication continues. If a statement produces different errors on the source and the replica, the replication SQL thread ...
https://dev.mysql.com/doc/refman/9.7/en/replication-formats.html
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 binary log in different formats according to the type of event. The different replication ...
https://dev.mysql.com/doc/refman/9.7/en/replication-gtids-failover.html
There are a number of techniques when using MySQL Replication with Global Transaction Identifiers (GTIDs) for provisioning a new replica which can then be used for scaleout, being promoted to source as necessary for failover. Each identifier ...
https://dev.mysql.com/doc/refman/9.7/en/replication-howto-additionalslaves.html
You can add another replica to an existing replication configuration without stopping the source server. To do this, you can set up the new replica by copying the data directory of an existing replica, and giving the new replica a different server ...
https://dev.mysql.com/doc/refman/9.7/en/replication-howto-masterstatus.html
To configure the replica to start the replication process at the correct point, you need to note the source's current coordinates within its binary log. Warning This procedure uses FLUSH TABLES WITH READ LOCK, which blocks COMMIT operations for ...
https://dev.mysql.com/doc/refman/9.7/en/replication-howto-slavebaseconfig.html
Each replica must have a unique server ID, as specified by the server_id system variable. If you are setting up multiple replicas, each one must have a unique server_id value that differs from that of the source and from any of the other replicas.
https://dev.mysql.com/doc/refman/9.7/en/replication-mode-change-online-verify-transactions.html
This section explains how to monitor a replication topology and verify that all anonymous transactions have been replicated. This is helpful when changing the replication mode online as you can verify that it is safe to change to GTID transactions.
https://dev.mysql.com/doc/refman/9.7/en/replication-multi-source-reset-replica.html
The RESET REPLICA statement can be used to reset a multi-source replica. By default, if you use the RESET REPLICA statement on a multi-source replica all channels are reset. Optionally, use the FOR CHANNEL channel clause to reset only a specific ...
https://dev.mysql.com/doc/refman/9.7/en/replication-options-binary-log.html
Startup Options Used with Binary Logging System Variables Used with Binary Logging You can use the mysqld options and system variables that are described in this section to affect the operation of the binary log as well as to control which ...
https://dev.mysql.com/doc/refman/9.7/en/replication-semisync-monitoring.html
The plugins for semisynchronous replication expose a number of status variables that enable you to monitor their operation. To check the current values of the status variables, use SHOW STATUS: mysql> SHOW STATUS LIKE 'Rpl_semi_sync%'; All ...