Search Results
https://dev.mysql.com/doc/refman/8.4/en/group-replication-multi-primary-mode.html
One result of these compatibility checks is particularly important in multi-primary mode. In multi-primary mode (group_replication_single_primary_mode=OFF) no member has a special role. Any member that is compatible with the other group members is ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-network-partitioning.html
Therefore it is important before forcing a new membership configuration to ensure that the servers to be excluded are indeed shut down and if they are not, shut them down before proceeding. The group needs to achieve consensus whenever a change ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-observability.html
This is where the instrumentation of Group Replication and Performance Schema becomes important. There is a lot of automation built into the Group Replication plugin. Nonetheless, you might sometimes need to understand what is happening behind the ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-online-upgrade-considerations.html
When upgrading an online group you should consider the following points: Regardless of the way which you upgrade your group, it is important to disable any writes to group members until they are ready to rejoin the group. When a member is stopped, ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-replication-group-member-stats.html
To use this table to monitor a Group Replication member, issue the following statement: mysql> SELECT * FROM performance_schema.replication_group_member_stats\G You can also use the following statement: mysql> TABLE ... Each member in a replication ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-responses-failure-expel.html
It is important to ensure that XCom's message cache is sufficiently large to contain the expected volume of messages in your specified time period, plus the initial 5-second detection period, otherwise members cannot reconnect. You can use the ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-restarting-group.html
Group Replication is designed to ensure that the database service is continuously available, even if some of the servers that form the group are currently unable to participate in it due to planned maintenance or unplanned issues. As long as the ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-single-primary-mode.html
This factor acts as a guaranteed and predictable tie-breaker so that all group members reach the same decision if it cannot be determined by any important factors. In single-primary mode (group_replication_single_primary_mode=ON) the group has a ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-upgrading-member.html
Important If an upgraded member has group_replication_start_on_boot=1 then it could rejoin the group before you can perform the MySQL upgrade procedure and could result in issues. This section explains the steps required for upgrading a member of a ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-use-cases.html
It is important to understand that although the database service is available, in the event of an unexpected server exit, those clients connected to it must be redirected, or failed over, to a different server. Group Replication enables you to ...