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/replica-logs-status.html
A replica server creates two replication metadata repositories, the connection metadata repository and the applier metadata repository. If binary log file position based replication is in use, when the replica restarts, it reads the two ...
https://dev.mysql.com/doc/refman/9.7/en/replication-bugs.html
For example, if you update the replica outside of the replication threads, the data goes out of synchrony, and you can have unique key violations on updates. When you have determined that there is no user error involved, and replication still ...
https://dev.mysql.com/doc/refman/9.7/en/replication-gtids-failover.html
Each identifier uniquely identifies a set of binary log events that together make up a transaction. There are a number of techniques when using MySQL Replication with Global Transaction Identifiers (GTIDs) for provisioning a new replica which can ...
https://dev.mysql.com/doc/refman/9.7/en/replication-multi-source.html
This is because the server IDs of replicas must be unique in a replication topology. Multi-source replication in MySQL 9.7 enables a replica to receive transactions from multiple immediate sources in parallel. In a multi-source replication ...
https://dev.mysql.com/doc/refman/9.7/en/replication-options-gtids.html
GTID transactions have a unique identifier that is used to refer to transactions. The MySQL Server system variables described in this section are used to monitor and control Global Transaction Identifiers (GTIDs). For additional information, see ...
https://dev.mysql.com/doc/refman/9.7/en/replication-options-reference.html
The following two sections provide basic information about the MySQL command-line options and system variables applicable to replication and the binary log. Replication Options and Variables The command-line options and system variables in the ...
https://dev.mysql.com/doc/refman/9.7/en/replication-privilege-checks-gr.html
Group Replication requires every table that is to be replicated by the group to have a defined primary key, or primary key equivalent where the equivalent is a non-null unique key. You can also use a PRIVILEGE_CHECKS_USER account to secure the two ...
https://dev.mysql.com/doc/refman/9.7/en/replication-problems.html
Verify that the server_id system variable was set at startup on both the source and replica and that the ID value is unique on each server. If you have followed the instructions but your replication setup is not working, the first thing to do is ...
https://dev.mysql.com/doc/refman/9.7/en/replication-rules-channel-based-filters.html
This is because the server IDs of replicas must be unique in a replication topology. This section explains how to work with replication filters when multiple replication channels exist, for example in a multi-source replication topology.
https://dev.mysql.com/doc/refman/9.7/en/rewriter-query-rewrite-plugin-reference.html
Users communicate with the plugin by modifying the set of rules stored in this table. The plugin communicates information to users by setting the table's message column. Note The rules table is loaded into the plugin by the flush_rewrite_rules ...