Search Results
https://dev.mysql.com/doc/refman/8.4/en/performance-schema-setup-instruments-table.html
For some instruments, modifications are effective only at server startup; changing them at runtime has no effect. This affects primarily mutexes, conditions, and rwlocks in the server, although there may be other instruments for which this is true.
https://dev.mysql.com/doc/refman/8.4/en/replication-features-memory.html
When a replication source server shuts down and restarts, its MEMORY tables become empty. This generated event is identifiable by a comment in the binary log, and if GTIDs are in use on the server, it has a GTID assigned. The statement is always ...
https://dev.mysql.com/doc/refman/8.4/en/replication-features-timezone.html
By default, source and replica servers assume that they are in the same time zone. If you are replicating between servers in different time zones, the time zone must be set on both source and replica. Verify that your combination of settings for ...
https://dev.mysql.com/doc/refman/8.4/en/replication-features-triggers.html
If you upgrade servers in a replication topology that use a version earlier than MySQL 5.7, upgrade the replicas first and then upgrade the source. If an upgraded replication source server still has old replicas using MySQL versions that do not ...
https://dev.mysql.com/doc/refman/8.4/en/replication-gtids.html
In addition, once a transaction with a given GTID is committed on a given server, any subsequent transaction having the same GTID is ignored by that server. This section discusses the following topics: How GTIDs are defined and created, and how they ... This section explains transaction-based replication using global transaction identifiers ...
https://dev.mysql.com/doc/refman/8.4/en/replication-multi-source.html
You might choose to implement multi-source replication to achieve goals like these: Backing up multiple servers to a single server. This is because the server IDs of replicas must be unique in a replication topology. The source distinguishes ...
https://dev.mysql.com/doc/refman/8.4/en/replication-rules-channel-based-filters.html
This is because the server IDs of replicas must be unique in a replication topology. The source distinguishes replicas only by their server IDs, not by the names of the replication channels, so it cannot recognize different replication channels from ... This section explains how to work with replication filters when multiple replication channels exist, for example in a multi-source replication ...
https://dev.mysql.com/doc/refman/8.4/en/replication-semisync.html
Failover from source to replica in this case might result in failover to a server that is missing transactions relative to the source. If your goal is to implement a fault-tolerant replication topology where all the servers receive the same ... In ...
https://dev.mysql.com/doc/refman/8.4/en/replication-threads-monitor-main.html
On the source server, the output from SHOW PROCESSLIST looks like this: mysql> SHOW PROCESSLIST\G *************************** 1. If you see no Binlog Dump threads on a source server, this means that replication is not running; that is, no replicas ... The SHOW PROCESSLIST statement provides information that tells you what is happening on the source and on the replica regarding ...
https://dev.mysql.com/doc/refman/8.4/en/replication.html
Replication enables data from one MySQL database server (known as a source) to be copied to one or more MySQL database servers (known as replicas). In this environment, all writes and updates must take place on the source server. The original type ...Replication is asynchronous by default; replicas do not need to be connected permanently to receive updates from a ...