Bug #89686 | Need to add "offset is provided by server_id and increment is 7" to GR manual. | ||
---|---|---|---|
Submitted: | 16 Feb 2018 7:47 | Modified: | 30 Apr 2019 11:04 |
Reporter: | Meiji Kimura | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
Version: | 5.7, 8.0 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | group replication |
[16 Feb 2018 7:47]
Meiji Kimura
[16 Feb 2018 8:34]
MySQL Verification Team
Hello Meiji-San, Thank you for the report! Thanks, Umesh
[30 Apr 2019 11:04]
Margaret Fisher
Posted by developer: Hi - Thanks for pointing this out. I have updated the descriptions for auto_increment_increment, auto_increment_offset, and group_replication_auto_increment_increment, and added to the FAQs as follows: Why did the auto increment setting on the server change? When Group Replication is started on a server, the value of auto_increment_increment is changed to the value of group_replication_auto_increment_increment, which defaults to 7, and the value of auto_increment_offset is changed to the server ID. The changes are reverted when Group Replication is stopped. These settings avoid the selection of duplicate auto-increment values for writes on group members, which causes rollback of transactions. The default auto increment value of 7 for Group Replication represents a balance between the number of usable values and the permitted maximum size of a replication group (9 members). The changes are only made and reverted if auto_increment_increment and auto_increment_offset each have their default value of 1. If their values have already been modified from the default, Group Replication does not alter them. From MySQL 8.0, the system variables are also not modified when Group Replication is in single-primary mode, where only one server writes. I don't think this is a limitation as such so I didn't add it there. Thanks for helping us to improve the documentation!