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-lifecycle.html
From MySQL 8.0, this restriction does not apply, and you can also choose whether to replace the whole GTID set in gtid_purged with a specified GTID set, or to add a specified GTID set to the GTIDs already in gtid_purged. The life cycle of a GTID ...
https://dev.mysql.com/doc/refman/8.0/en/replication-howto-slaveinit.html
To set up the replica to communicate with the source for replication, configure the replica with the necessary connection information. You must be able to connect to the source MySQL server using TCP/IP. The CHANGE REPLICATION SOURCE TO | CHANGE ...
https://dev.mysql.com/doc/refman/8.0/en/replication-multi-source-provision-replica.html
In MySQL 5.6 and 5.7, the statement replaces the value of gtid_purged on the replica, and also in those releases that value can only be changed when the replica's record of transactions with GTIDs (the gtid_executed set) is empty. If the sources in ...
https://dev.mysql.com/doc/refman/8.0/en/replication-options.html
(In MySQL 8.0.22, the SLAVE keyword was replaced by REPLICA.) Note Issuing a STOP REPLICA or RESET REPLICA statement does not reset the source's UUID as used on the replica. The following sections contain information about mysqld options and server ...
https://dev.mysql.com/doc/refman/8.0/en/replication-rules-channel-based-filters.html
If multiple types of filters (do_db, do_ignore_table, wild_do_table, and so on) are specified, only the specified filter types are replaced by the statement. This section explains how to work with replication filters when multiple replication ...
https://dev.mysql.com/doc/refman/8.0/en/replication-rules-db-options.html
In those cases, the database being created, altered, or dropped replaces the default database when determining whether to log or ignore updates. When evaluating replication options, the replica begins by checking to see whether there are any ...
https://dev.mysql.com/doc/refman/8.0/en/replication-sbr-rbr.html
Not all statements which modify data (such as INSERT DELETE, UPDATE, and REPLACE statements) can be replicated using statement-based replication. For most users, the mixed replication format should provide the best combination of data integrity and ...
https://dev.mysql.com/doc/refman/8.0/en/replication-semisync-installation.html
The new plugins replace the terms “master” and “slave” with “source” and “replica” in system variables and status variables, and you can (and should) install these versions instead of the old ones (which are now deprecated, and thus ... Semisynchronous replication is implemented using plugins, which must be installed on the source and on the replicas to make semisynchronous replication available on the ...
https://dev.mysql.com/doc/refman/8.0/en/replication-semisync-interface.html
To check the current values of the status variables for semisynchronous replication, use SHOW VARIABLES: mysql> SHOW VARIABLES LIKE 'rpl_semi_sync%'; Beginning with MySQL 8.0.26, new versions of the source and replica plugins are supplied, which ...
https://dev.mysql.com/doc/refman/8.0/en/replication-semisync-monitoring.html
To check the current values of the status variables, use SHOW STATUS: mysql> SHOW STATUS LIKE 'Rpl_semi_sync%'; Beginning with MySQL 8.0.26, new versions of the source and replica plugins are supplied, which replace the terms “master” and ...