Search Results
https://dev.mysql.com/doc/refman/8.4/en/replication-encrypted-connections.html
For example: mysql> CREATE USER 'repl'@'%.example.com' IDENTIFIED BY 'password' -> REQUIRE SSL; mysql> GRANT REPLICATION SLAVE ON *.* -> TO 'repl'@'%.example.com'; If you have an existing replication user account on the source, you can add REQUIRE ... To use an encrypted connection for the transfer of the binary log required during replication, both the source and the replica servers must support encrypted network ...
https://dev.mysql.com/doc/refman/8.4/en/replication-features-differing-tables.html
Source and target tables for replication do not have to be identical. A table on the source can have more or fewer columns than the replica's copy of the table. In addition, corresponding table columns on the source and the replica can use ...
https://dev.mysql.com/doc/refman/8.4/en/replication-features-row-searches.html
For each record in the target table, it determines whether that row exists in the hash table. When a replica using row-based replication format applies an UPDATE or DELETE operation, it must search the relevant table for the matching rows. The ...
https://dev.mysql.com/doc/refman/8.4/en/replication-features-temptables.html
The exception is that to enable correct removal of temporary tables at the end of a session, a replica always replicates a DROP TEMPORARY TABLE IF EXISTS statement, regardless of any exclusion rules that would normally apply for the specified table.
https://dev.mysql.com/doc/refman/8.4/en/replication-functions-async-failover.html
The following functions enable you to add or remove replication source servers to or from the source list for a replication channel, as well as clear the source list for a given server. The connection is also changed if the currently connected ...
https://dev.mysql.com/doc/refman/8.4/en/replication-gtids-concepts.html
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 is unique not only to the server on which it originated, but is unique across ...
https://dev.mysql.com/doc/refman/8.4/en/replication-mode-change-online-enable-gtids.html
Ideally, you should wait for the server to purge all binary logs that existed when the previous step was completed, and for any backup taken before then to expire. This section describes how to enable GTID transactions, and optionally ...
https://dev.mysql.com/doc/refman/8.4/en/replication-options-source.html
This section describes the server options and system variables that you can use on replication source servers. You can specify the options either on the command line or in an option file. On the source and each replica, you must set the server_id ...
https://dev.mysql.com/doc/refman/8.4/en/replication-options.html
In addition, the replication receiver thread generates a warning if either of the following is true: No source having the expected server_uuid exists. The following sections contain information about mysqld options and server variables that are ...
https://dev.mysql.com/doc/refman/8.4/en/replication-privilege-checks.html
By default, MySQL replication (including Group Replication) does not carry out privilege checks when transactions that were already accepted by another server are applied on a replica or group member. You can create a user account with the ...