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-binlog-encryption-key-rotation.html
You can rotate the binary log master key on a regular basis to comply with your organization's security policy, and also if you suspect that the current or any of the previous binary log master keys might have been compromised. Then investigate the ... When binary log encryption is enabled, you can rotate the binary log master key at any time while the server is running by issuing ALTER INSTANCE ROTATE BINLOG MASTER ...
https://dev.mysql.com/doc/refman/8.0/en/replication-channels.html
This section describes how channels can be used in a replication topology, and the impact they have on single-source replication. Each replication channel must have a unique (nonempty) name, as explained in Section 19.2.2.4, “Replication Channel ... In MySQL multi-source replication, a replica opens multiple replication channels, one for each source ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-errors.html
Note If a temporary error is recorded in the replica's error log, you do not necessarily have to take any action suggested in the quoted error message. For nontransactional storage engines such as MyISAM, it is possible to have a statement that only ... If a statement produces the same error (identical error code) on both the source and the replica, the error is logged, but replication ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-triggers.html
If you want triggers to execute on both the source and the replica, perhaps because you have different triggers on the source and replica, you must use statement-based replication. (Bug #45677) A trigger can have triggers for different combinations ... With statement-based replication, triggers executed on the source also execute on the ...
https://dev.mysql.com/doc/refman/8.0/en/replication-functions-synchronization.html
If binary log transaction compression is in use and the transaction payload at the specified position is compressed (as a Transaction_payload_event), the function waits until the whole transaction has been read and applied, and the positions have ...
https://dev.mysql.com/doc/refman/8.0/en/replication-gtids-failover.html
The source's global gtid_purged variable contains the set of all transactions that have been purged from the source's binary log. When restoring a replica in a GTID based replication setup that has encountered an error, injecting an empty ... There ...
https://dev.mysql.com/doc/refman/8.0/en/replication-mode-change-online-disable-gtids.html
However, if you have the possibility to take the servers offline when disabling GTIDs mode that process is easier. See Section 19.1.4.4, “Verifying Replication of Anonymous Transactions”, for one method of checking that all anonymous ... This ...
https://dev.mysql.com/doc/refman/8.0/en/replication-multi-source-provision-replica.html
If the sources in the multi-source replication topology have existing data, it can save time to provision the replica with the relevant data before starting replication. You can clear a replica's GTID execution history by issuing RESET MASTER on ...
https://dev.mysql.com/doc/refman/8.0/en/replication-options-reference.html
gtid_executed_compression_period: Compress gtid_executed table each time this many transactions have occurred. gtid_purged: Set of all GTIDs that have been purged from binary log. The following two sections provide basic information about the MySQL ...
https://dev.mysql.com/doc/refman/8.0/en/replication-privilege-checks-account.html
The user account that is specified using the CHANGE REPLICATION SOURCE TO | CHANGE MASTER TO statement as the PRIVILEGE_CHECKS_USER account for a replication channel must have the REPLICATION_APPLIER privilege, otherwise the replication applier ...