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-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: Up to MySQL 8.0.20, when a suspicion is created, it times out ...
https://dev.mysql.com/doc/refman/8.0/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.0/en/group-replication-responses-failure-expel.html
You can use the group_replication_member_expel_timeout system variable, which is available from MySQL 8.0.13, to allow additional time between the creation of a suspicion and the expulsion of the suspect member. There is an initial 5-second ...A ...
https://dev.mysql.com/doc/refman/8.0/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. From MySQL 8.0.27, the group communication engine can use a single leader to drive consensus ...
https://dev.mysql.com/doc/refman/8.0/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.0/en/group-replication-performance-message-fragmentation.html
When an abnormally large message is sent between Group Replication group members, it can result in some group members being reported as failed and expelled from the group. This is because the single thread used by Group Replication's group ...From ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication-secure-user.html
State transfer from the binary log requires a replication user with the correct permissions so that Group Replication can establish direct member-to-member replication channels. The same replication user is used for distributed recovery on all the ...For detailed instructions to set up this user, see Section 20.2.1.3, “User Credentials For Distributed ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication-single-primary-mode.html
In single-primary mode (group_replication_single_primary_mode=ON) the group has a single primary server that is set to read/write mode. All the other members in the group are set to read-only mode (with super_read_only=ON). All other servers that ...The following diagram shows this process: Figure 20.4 New Primary Election When a new primary is chosen, it might have a backlog of changes that had been applied on the old primary but have not yet been applied on the new ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication-distributed-recovery-fault.html
Group Replication's distributed recovery process has a number of built-in measures to ensure fault tolerance in the event of any problems during the process. The donor for distributed recovery is selected randomly from the existing list of suitable ...In MySQL 8.0.17 and later, for state transfer from the binary log, the joiner only selects a donor that is running a lower or equal patch version of MySQL Server compared to ...
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-tp-thread-group-state-table.html
Prior to MySQL 8.0.14, use the corresponding INFORMATION_SCHEMA table instead; see Section 28.5.2, “The INFORMATION_SCHEMA TP_THREAD_GROUP_STATE Table”. The tp_thread_group_state table has one row per thread group in the thread pool. Each row ...