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-gtids-concepts.html
Note that the mysql.gtid_executed table is cleared if you issue RESET MASTER. 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 ...
https://dev.mysql.com/doc/refman/8.0/en/replication-gtids-failover.html
Rather than copy the binary logs when taking a snapshot to provision a new server, you can instead note the content of gtid_executed on the server from which the snapshot was taken. There are a number of techniques when using MySQL Replication with ...
https://dev.mysql.com/doc/refman/8.0/en/replication-gtids-functions.html
This section provides examples of stored functions (see Chapter 27, Stored Objects) which you can create using some of the built-in functions provided by MySQL for use with GTID-based replication, listed here: GTID_SUBSET(): Shows whether one GTID ...
https://dev.mysql.com/doc/refman/8.0/en/replication-gtids-restrictions.html
Note that --enforce-gtid-consistency only takes effect if binary logging takes place for a statement. Because GTID-based replication is dependent on transactions, some features otherwise available in MySQL are not supported when using it. This ...
https://dev.mysql.com/doc/refman/8.0/en/replication-howto-additionalslaves.html
Note If the replication source server or existing replica that you are copying to create the new replica has any scheduled events, ensure that these are disabled on the new replica before you start it. You can add another replica to an existing ...
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-howto.html
Note Certain steps within the setup process require the SUPER privilege. This section describes how to set up a MySQL server to use binary log file position based replication. There are a number of different methods for setting up replication, and ...
https://dev.mysql.com/doc/refman/8.0/en/replication-mode-change-online-verify-transactions.html
A safer method in the sense that it does not depend on timing: if you only have a source with one or more replicas, do the following: On the source, execute: SHOW MASTER STATUS; Note down the values in the File and Position column. This section ...
https://dev.mysql.com/doc/refman/8.0/en/replication-multi-source-adding-binlog-master.html
These steps assume that binary logging is enabled on the source (which is the default), the replica is using TABLE based replication applier metadata repositories (which is the default in MySQL 8.0), and that you have enabled a replication user and ...Use the CHANGE REPLICATION SOURCE TO statement (from MySQL 8.0.23) or CHANGE MASTER TO statement (before MySQL 8.0.23) to configure a replication channel for each source on the replica (see Section 19.2.2, “Replication ...