PDF (US Ltr)
- 35.0Mb
PDF (A4)
- 35.1Mb
Man Pages (TGZ)
- 255.5Kb
Man Pages (Zip)
- 360.4Kb
Info (Gzip)
- 3.4Mb
Info (Zip)
- 3.4Mb
Search Results
https://dev.mysql.com/doc/refman/5.7/en/replication-features-max-allowed-packet.html
max_allowed_packet sets an upper limit on the size of any single message between the MySQL server and clients, including replicas. If you are replicating large column values (such as might be found in TEXT or BLOB columns) and max_allowed_packet is ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-transactions.html
In general, you should avoid transactions that update both transactional and nontransactional tables in a replication environment. You should also avoid using any statement that accesses both transactional (or temporary) and nontransactional tables ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-triggers.html
With statement-based replication, triggers executed on the source also execute on the replica. With row-based replication, triggers executed on the source do not execute on the replica. Instead, the row changes on the source resulting from trigger ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features.html
The following sections provide information about what is supported and what is not in MySQL replication, and about specific issues and situations that may occur when replicating certain statements. Statement-based replication depends on ...
https://dev.mysql.com/doc/refman/5.7/en/replication-gtids-restrictions.html
Because GTID-based replication is dependent on transactions, some features otherwise available in MySQL are not supported when using it. This section provides information about restrictions on and limitations of replication with GTIDs. When using ...
https://dev.mysql.com/doc/refman/5.7/en/replication-howto-masterbaseconfig.html
To configure a source to use binary log file position based replication, you must ensure that binary logging is enabled, and establish a unique server ID. Each server within a replication topology must be configured with a unique server ID, which ...
https://dev.mysql.com/doc/refman/5.7/en/replication-howto-repuser.html
Each replica connects to the source using a MySQL user name and password, so there must be a user account on the source that the replica can use to connect. The user name is specified by the MASTER_USER option on the CHANGE MASTER TO command when ...
https://dev.mysql.com/doc/refman/5.7/en/replication-multi-source-monitoring.html
row *************************** CHANNEL_NAME: source_1 GROUP_NAME: SOURCE_UUID: 046e41f8-a223-11e4-a975-0811960cc264 THREAD_ID: 24 SERVICE_STATE: ON COUNT_RECEIVED_HEARTBEATS: 0 LAST_HEARTBEAT_TIMESTAMP: 0000-00-00 00:00:00 RECEIVED_TRANSACTION_SET: ... To monitor the status of replication channels the following options exist: Using the replication Performance Schema ...
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-rbr-usage.html
MySQL uses statement-based logging (SBL), row-based logging (RBL) or mixed-format logging. The type of binary log used impacts the size and efficiency of logging. Therefore the choice between row-based replication (RBR) or statement-based ...