PDF (US Ltr)
- 41.8Mb
PDF (A4)
- 41.9Mb
Man Pages (TGZ)
- 272.4Kb
Man Pages (Zip)
- 378.4Kb
Info (Gzip)
- 4.2Mb
Info (Zip)
- 4.2Mb
Search Results
https://dev.mysql.com/doc/refman/9.7/en/replication-binlog-encryption-scope.html
Existing binary log files and relay log files that were present on the server when you started encryption are not encrypted. You can purge these files when they are no longer needed. Data in motion in the replication event stream, which is sent to ...
https://dev.mysql.com/doc/refman/9.7/en/replication-features-transaction-inconsistencies.html
That is, all transactions up to point N have been applied, and no transactions after N have been applied, but Exec_master_log_pos has a value smaller than N. Inconsistencies in the sequence of transactions that have been executed from the relay log ...
https://dev.mysql.com/doc/refman/9.7/en/replication-gtids-auto-positioning.html
GTIDs replace the file-offset pairs previously required to determine points for starting, stopping, or resuming the flow of data between source and replica. When GTIDs are in use, all the information that the replica needs for synchronizing with ...
https://dev.mysql.com/doc/refman/9.7/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/9.7/en/replication-mode-change-online-enable-gtids.html
If you use binary logs for anything other than replication, such as point-in-time backup and restore, wait until you no longer need the old binary logs containing transactions without GTIDs. This section describes how to enable GTID transactions, ...
https://dev.mysql.com/doc/refman/9.7/en/replication-options-reference.html
replica_checkpoint_group: Maximum number of transactions processed by multithreaded replica before checkpoint operation is called to update progress status. replica_checkpoint_period: Update progress status of multithreaded replica and flush relay ... The following two sections provide basic information about the MySQL command-line options and system variables applicable to replication and the binary ...
https://dev.mysql.com/doc/refman/9.7/en/replication-privilege-checks-recover.html
For instructions to do this, see Section 9.5, “Point-in-Time (Incremental) Recovery”. If a privilege check against the PRIVILEGE_CHECKS_USER account fails, the transaction is not executed and replication stops for the channel. Details of the ...
https://dev.mysql.com/doc/refman/9.7/en/replication-privilege-checks.html
When you restart the replication channel, checks on dynamic privileges are applied from that point on. By default, MySQL replication (including Group Replication) does not carry out privilege checks when transactions that were already accepted by ...
https://dev.mysql.com/doc/refman/9.7/en/replication-semisync-interface.html
The rpl_semi_sync_source_wait_point system variable controls the point at which a semisynchronous source server waits for replica acknowledgment of transaction receipt before returning a status to the client that committed the transaction. When you ...
https://dev.mysql.com/doc/refman/9.7/en/replication-semisync.html
At this point, the transaction has committed on the source side, and receipt of its events has been acknowledged by at least one replica. As an alternative, you can configure the source so that the source waits for replica acknowledgment after ...