Search Results
https://dev.mysql.com/doc/refman/8.4/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. Because the temporary files are volatile and tied to a single process, they are encrypted using single-tier encryption, ...
https://dev.mysql.com/doc/refman/8.4/en/replication-features-directory.html
This can cause problems if no corresponding directory exists in the replica host file system or if it exists but is not accessible to the replica MySQL server. If a DATA DIRECTORY or INDEX DIRECTORY table option is used in a CREATE TABLE statement ...
https://dev.mysql.com/doc/refman/8.4/en/replication-gtids-failover.html
This poses some challenges when provisioning a new server with data from another existing server. This method has the advantage that a new server is available almost immediately; only those transactions that were committed while the snapshot or dump ... There are a number of techniques when using MySQL Replication with Global Transaction Identifiers (GTIDs) for provisioning a new replica which can then be used for scaleout, being promoted to source as necessary for ...
https://dev.mysql.com/doc/refman/8.4/en/replication-howto-masterstatus.html
The next step depends on whether you have existing data on the source. Choose one of the following options: If you have existing data that needs be to synchronized with the replica before you start replication, leave the client running so that the ... 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 ...
https://dev.mysql.com/doc/refman/8.4/en/replication-multi-source-monitoring.html
To monitor the status of replication channels the following options exist: Using the replication Performance Schema tables. You can choose to monitor all channels, or a subset of the existing channels. This enables you to write complex queries ...
https://dev.mysql.com/doc/refman/8.4/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. SET @@GLOBAL.gtid_purged adds the GTID set from the dump file to the existing ...In a multi-source replication topology, cloning or copying of the data directory cannot be used to provision the replica with data from all of the sources, and you might also want to replicate only specific databases from each ...
https://dev.mysql.com/doc/refman/8.4/en/replication-options-replica.html
With row-based format, DML statements are translated based on the database where the modified table exists. --slave-skip-errors=[err_code1,err_code2,...|all|ddl_exist_errors] Command-Line Format --slave-skip-errors=name Deprecated Yes System ...
https://dev.mysql.com/doc/refman/8.4/en/replication-rules-examples.html
With row-based format, DML statements are handled based on the database where the modified table exists. However, the result of the DML INSERT statement is different depending on the binary logging format: If row-based binary logging format is in ...
https://dev.mysql.com/doc/refman/8.4/en/replication-solutions-backups-rawdata.html
This requires that the binary logs still exist on the source server. If your replica is replicating LOAD DATA statements, you should also back up any SQL_LOAD-* files that exist in the directory that the replica uses for this purpose. To guarantee ...
https://dev.mysql.com/doc/refman/8.4/en/replication-solutions-diffengines.html
If a specific engine does not exist for a table to be created, MySQL uses the default engine type, usually InnoDB. If you are already running a replication solution and want to convert your existing tables to another engine type, follow these steps: ... It does not matter for the replication process whether the original table on the source and the replicated table on the replica use different storage engine ...