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-formats.html
Setting the variable globally takes effect for clients that connect after the change, but not for any current client sessions, including the session where the variable setting was changed. Replication works because events written to the binary log ...
https://dev.mysql.com/doc/refman/8.0/en/replication-gtids-failover.html
Ensure that all of the binary log files are processed using a single mysql process, rather than multiple connections. There are a number of techniques when using MySQL Replication with Global Transaction Identifiers (GTIDs) for provisioning a new ...
https://dev.mysql.com/doc/refman/8.0/en/replication-howto-additionalslaves.html
The new replica now uses the information in its connection metadata repository to start the replication process. You can add another replica to an existing replication configuration without stopping the source server. To do this, you can set up the ...
https://dev.mysql.com/doc/refman/8.0/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/8.0/en/replication-howto-slavebaseconfig.html
You can change the server_id value dynamically by issuing a statement like this: SET GLOBAL server_id = 21; Note that a value of 0 for the server ID prevents a replica from connecting to a source. Each replica must have a unique server ID, as ...
https://dev.mysql.com/doc/refman/8.0/en/replication-mode-change-online-verify-transactions.html
If you use a circular replication topology where multiple servers may have write clients, perform step 2 for each source-replica connection, until you have completed the full circle. This section explains how to monitor a replication topology and ...
https://dev.mysql.com/doc/refman/8.0/en/replication-multi-source-reset-replica.html
RESET REPLICA makes the replica forget its replication position, and clears the relay log, but it does not change any replication connection parameters (such as the source host name) or replication filters. The RESET REPLICA statement can be used ...
https://dev.mysql.com/doc/refman/8.0/en/replication-options-binary-log.html
However, problems arise when modifications done to nontransactional tables on behalf of a transaction become immediately visible to other connections because these changes may not be written immediately into the binary log. The maximum possible ...
https://dev.mysql.com/doc/refman/8.0/en/replication-semisync-installation.html
Semisynchronous replication is implemented using plugins, which must be installed on the source and on the replicas to make semisynchronous replication available on the instances. There are different plugins for a source and for a replica. After a ...
https://dev.mysql.com/doc/refman/8.0/en/replication-semisync-monitoring.html
Some examples are: Rpl_semi_sync_source_clients or Rpl_semi_sync_master_clients The number of semisynchronous replicas that are connected to the source server. The plugins for semisynchronous replication expose a number of status variables that ...