Search Results
https://dev.mysql.com/doc/refman/8.4/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.4/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.4/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.4/en/replication-mode-change-online-verify-transactions.html
If you emply a circular replication topology where multiple servers may have write clients, perform the second step for each source-replica connection, until you have completed the full circle. This section explains how to monitor a replication ...
https://dev.mysql.com/doc/refman/8.4/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.4/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.4/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.4/en/replication-solutions-unexpected-replica-halt.html
The following combination of settings on a replica is the most resilient to unexpected halts: When GTID-based replication is in use (gtid_mode=ON), set SOURCE_AUTO_POSITION=1, which activates GTID auto-positioning for the connection to the source to ... In order for replication to be resilient to unexpected halts of the server (sometimes described as crash-safe) it must be possible for the replica to recover its state before ...
https://dev.mysql.com/doc/refman/8.4/en/replication.html
Replication is asynchronous by default; replicas do not need to be connected permanently to receive updates from a source. Replication enables data from one MySQL database server (known as a source) to be copied to one or more MySQL database ...
https://dev.mysql.com/doc/refman/8.4/en/rewriter-query-rewrite-plugin-installation.html
To verify that, connect to the server and execute this statement: mysql> SHOW GLOBAL VARIABLES LIKE 'rewriter_enabled'; +------------------+-------+ | Variable_name | Value | +------------------+-------+ | rewriter_enabled | ON | ... Note If ...