Search Results
https://dev.mysql.com/doc/refman/8.4/en/group-replication-understanding-consistency-guarantees.html
In terms of distributed consistency guarantees, either in normal or failure repair operations, Group Replication has always been an eventual consistency system. This means that as soon as the incoming traffic slows down or stops, all group members ...The events that relate to the consistency of a system can be split into control operations, either manual or automatically triggered by failures; and data flow ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-distributed-recovery-connections.html
When state transfer from the donor's binary log is in progress over this connection (using the asynchronous replication channel group_replication_recovery), the joining member acts as the replica and the existing member acts as the source. When a ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-distributed-recovery.html
Whenever a member joins or rejoins a replication group, it must catch up with the transactions that were applied by the group members before it joined, or while it was away. The joining member begins by checking the relay log for its ...After this, ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-configuring-consistency-guarantees.html
Although the Transaction Synchronization Points section explains that conceptually there are two synchronization points from which you can choose: on read or on write, these terms were a simplification and the terms used in Group Replication are: ...A read/write transaction does not wait for other members to apply a ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-member-actions.html
Group Replication has the ability to set actions for the members of a group to take in specified situations. The member actions configuration for a server can also be reset to the default after it has left the group. Administrators (with the ...In ...
https://dev.mysql.com/doc/refman/8.4/en/performance-schema-replication-group-communication-information-table.html
This table shows group configuration options for the whole replication group. The replication_group_communication_information table has these columns: WRITE_CONCURRENCY The maximum number of consensus instances that the group can execute in ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-failure-detection.html
Group Replication’s failure detection mechanism is a distributed service which is able to identify that a server in the group is not communicating with the others, and is therefore suspected of being out of service. If the group’s consensus is ...One channel is used to send messages to the member and the other channel is used to receive messages from the ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-single-consensus-leader.html
By default, the group communication engine for Group Replication (XCom, a Paxos variant) operates using every member of the replication group as a leader. The group communication engine can use a single leader to drive consensus when the group is ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-responses-failure-expel.html
You can use the group_replication_member_expel_timeout system variable to allow additional time between the creation of a suspicion and the expulsion of the suspect member. There is an initial 5-second detection period before a Group Replication ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-responses-failure.html
Group Replication's failure detection mechanism is designed to identify group members that are no longer communicating with the group, and expel them as and when it seems likely that they have failed. Having a failure detection mechanism increases ...By default, the following behaviors happen if a member is suspected of having failed: In MySQL 8.4, when a suspicion is created, a waiting period of 5 seconds is added before the suspicion times out and the suspected member is liable for ...