Bug #102706 | Update group replication docs replication configuration requirements | ||
---|---|---|---|
Submitted: | 23 Feb 2021 15:02 | Modified: | 13 Mar 2021 23:18 |
Reporter: | Eduardo Ortega | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
Version: | 8.0.21, 8.0.23 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[23 Feb 2021 15:02]
Eduardo Ortega
[24 Feb 2021 13:45]
MySQL Verification Team
Hello Eduardo, Thank you for the report and feedback. Verified as described. regards, Umesh
[24 Feb 2021 13:47]
MySQL Verification Team
MySQL Server 8.0.23 test results
Attachment: 102706_8.0.23.results (application/octet-stream, text), 15.70 KiB.
[24 Feb 2021 13:48]
MySQL Verification Team
Changing the category to Docs
[13 Mar 2021 23:18]
Margaret Fisher
Posted by developer: Thanks for the comment! It's actually noted in the Group Replication Requirements topic here, near where you were looking: https://dev.mysql.com/doc/refman/8.0/en/group-replication-requirements.html Multithreaded Appliers. Group Replication members can be configured as multithreaded replicas, enabling transactions to be applied in parallel. A nonzero value for slave_parallel_workers enables the multithreaded applier on the member, and up to 1024 parallel applier threads can be specified. Setting slave_preserve_commit_order=1 ensures that the final commit of parallel transactions is in the same order as the original transactions, as required for Group Replication, which relies on consistency mechanisms built around the guarantee that all participating members receive and apply committed transactions in the same order. Finally, the setting slave_parallel_type=LOGICAL_CLOCK, which specifies the policy used to decide which transactions are allowed to execute in parallel on the replica, is required with slave_preserve_commit_order=1. Setting slave_parallel_workers=0 disables parallel execution and gives the replica a single applier thread and no coordinator thread. With that setting, the slave_parallel_type and slave_preserve_commit_order options have no effect and are ignored. - It's too low level to put in the Getting Started topic, but I'll reword to clarify that it is a requirement, as the wording is a little unclear.