PDF (US Ltr)
- 43.3Mb
PDF (A4)
- 43.4Mb
Man Pages (TGZ)
- 297.2Kb
Man Pages (Zip)
- 402.4Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/group-replication-performance-xcom-cache-increase.html
However, if the transactions that happened during the member's absence have been deleted from the other members' XCom message caches because their maximum size limit was reached, the member cannot reconnect in this way. If a member is absent for a ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication-performance-xcom-cache.html
If the cache size limit is reached, XCom removes the oldest entries that have been decided and delivered. The group communication engine for Group Replication (XCom, a Paxos variant) includes a cache for messages (and their metadata) exchanged ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication-performance.html
Group Replication is designed to create fault-tolerant systems with built-in failure detection and automated recovery. If a member server instance leaves voluntarily or stops communicating with the group, the remaining members agree a ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication-primary-secondary-replication.html
It is a shared-nothing system, where all servers have a full copy of the data by default. Traditional MySQL Replication provides a simple source to replica approach to replication. The source is the primary, and there are one or more replicas, ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication-probes-and-statistics.html
The monitoring mechanism works by having each member deploying a set of probes to collect information about its work queues and throughput. It then propagates that information to the group periodically to share that data with the other members.
https://dev.mysql.com/doc/refman/8.0/en/group-replication-replication-group-member-stats.html
Statistics regarding the certifier and applier procedures are useful to understand how the applier queue is growing, how many conflicts have been found, how many transactions were checked, which transactions are committed everywhere, and so on.
https://dev.mysql.com/doc/refman/8.0/en/group-replication-responses-failure-partition.html
When the timeout specified by group_replication_unreachable_majority_timeout elapses, all pending transactions that have been processed by the member and the others in the minority group are rolled back, and the servers in that group move to the ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication-responses-failure-rejoin.html
While an auto-rejoin procedure is taking place, the Performance Schema table events_stages_current shows the event “Undergoing auto-rejoin procedure”, with the number of retries that have been attempted so far during this instance of the ... The ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication-throttling.html
As a consequence, if the quota is very small for the write requests issued some transactions may have latencies close to the monitoring period. Based on the metrics gathered across all servers in the group, a throttling mechanism kicks in and ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication-upgrade.html
While you are in the process of upgrading an online group, in order to maximize availability, you might need to have members with different MySQL Server versions running at the same time. This section explains how to upgrade a Group Replication ...