PDF (US Ltr)
- 35.1Mb
PDF (A4)
- 35.2Mb
Man Pages (TGZ)
- 256.4Kb
Man Pages (Zip)
- 361.2Kb
Info (Gzip)
- 3.4Mb
Info (Zip)
- 3.4Mb
Search Results
https://dev.mysql.com/doc/refman/5.7/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/5.7/en/replication-howto-masterbaseconfig.html
If these options already exist, but are commented out, uncomment the options and alter them according to your needs. To configure a source to use binary log file position based replication, you must ensure that binary logging is enabled, and ...
https://dev.mysql.com/doc/refman/5.7/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. In a multi-source replication topology, copying the data directory cannot be ...
https://dev.mysql.com/doc/refman/5.7/en/replication-options-binary-log.html
When inserting a row, only the after image is logged, since there is no existing row to be matched. Startup Options Used with Binary Logging System Variables Used with Binary Logging You can use the mysqld options and system variables that are ...
https://dev.mysql.com/doc/refman/5.7/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 System Variable ... This ...
https://dev.mysql.com/doc/refman/5.7/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/5.7/en/replication-options.html
In addition, the replication I/O 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 used in ...
https://dev.mysql.com/doc/refman/5.7/en/replication-semisync.html
Compared to asynchronous replication, semisynchronous replication provides improved data integrity, because when a commit returns successfully, it is known that the data exists in at least two places. In addition to the built-in asynchronous ...
https://dev.mysql.com/doc/refman/5.7/en/replication-solutions-unexpected-replica-halt.html
Note that this setting ignores the existing relay log files, in case they are corrupted or inconsistent. In order for replication to be resilient to unexpected halts of the server (sometimes described as crash-safe) it must be possible for the ...
https://dev.mysql.com/doc/refman/5.7/en/replication-upgrade.html
If you are upgrading an existing replication setup from a version of MySQL that does not support global transaction identifiers (GTIDs) to a version that does, only enable GTIDs on the source and the replicas when you have made sure that the setup ... When you upgrade servers that participate in a replication topology, you need to take into account each server's role in the topology and look out for issues specific to ...