Search Results
https://dev.mysql.com/doc/refman/8.4/en/replication-asynchronous-connection-failover-replica.html
Asynchronous connection failover for replicas is activated automatically for a replication channel on a Group Replication primary when you set SOURCE_CONNECTION_AUTO_FAILOVER=1 in the CHANGE REPLICATION SOURCE TO statement for the channel. The ...
https://dev.mysql.com/doc/refman/8.4/en/replication-gtids-lifecycle.html
The life cycle of a GTID consists of the following steps: A transaction is executed and committed on the source. This client transaction is assigned a GTID composed of the source's UUID and the smallest nonzero transaction sequence number not yet ...
https://dev.mysql.com/doc/refman/8.4/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/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. This enables you to write complex queries based on Channel_Name as a key. By default, if the FOR CHANNEL channel clause is ...
https://dev.mysql.com/doc/refman/8.4/en/replication-rules-db-options.html
When evaluating replication options, the replica begins by checking to see whether there are any --replicate-do-db or --replicate-ignore-db options that apply. When using --binlog-do-db or --binlog-ignore-db, the process is similar, but the options ...
https://dev.mysql.com/doc/refman/8.4/en/replication-solutions-partitioning.html
There may be situations where you have a single source server and want to replicate different databases to different replicas. For example, you may want to distribute different sales data to different departments to help spread the load during data ...
https://dev.mysql.com/doc/refman/8.4/en/replication-solutions-rbr-monitoring.html
The current progress of the replication applier (SQL) thread when using row-based replication is monitored through Performance Schema instrument stages, enabling you to track the processing of operations and check the amount of work completed and ...
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). Replication is asynchronous by default; replicas do not need to be connected permanently to receive ...
https://dev.mysql.com/doc/refman/8.4/en/request-access.html
After the server accepts a connection, it enters Stage 2 of access control. For each request that you issue through the connection, the server determines what operation you want to perform, then checks whether your privileges are sufficient. This ...
https://dev.mysql.com/doc/refman/8.4/en/resource-groups.html
MySQL supports creation and management of resource groups, and permits assigning threads running within the server to particular groups so that threads execute according to the resources available to the group. Group attributes enable control over ...