Bug #109615 | Timeout on wait for view after joining group | ||
---|---|---|---|
Submitted: | 13 Jan 2023 7:14 | Modified: | 17 Jan 2023 18:22 |
Reporter: | zetang zeng | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: Group Replication | Severity: | S3 (Non-critical) |
Version: | 5.7.40 | OS: | Any |
Assigned to: | MySQL Verification Team | CPU Architecture: | Any |
[13 Jan 2023 7:14]
zetang zeng
[13 Jan 2023 13:44]
MySQL Verification Team
Hi, Can you please let us know whether your have setup all your servers to be fully ACID-compliant ??? Please, read our Manual on how to configure your OS and InnoDB in order to be 100 % ACID compliant. Also, repeat your experiment after full ACID setup is made, including stringest InnoDB log flushing, OS full flushing, fsync / sync , complete disabling of the OS, filesystem and disk caches , etc , etc ....... You are welcome to contact us again, after you have configured ACID compatibility, as described above.
[14 Jan 2023 4:36]
zetang zeng
Any link to 'Manual on how to configure your OS and InnoDB in order to be 100 % ACID compliant.'? And doesn't this question only has to do with Group Replication? why os/ innodb config check?
[17 Jan 2023 18:22]
MySQL Verification Team
Hi, This has nothing to do with ACID, apologies for misinformation, anyhow, this behavior is not a bug, when you do a reboot of all servers you do a full cluster crash and there is no automatic recovery from that. You need to manually recover the system from such scenario. Thank you for using MySQL
[17 Jan 2023 19:05]
MySQL Verification Team
Additional info: - there must be on server capable to bootstrap the group. Look at documentation about "configuring instances" it is explained in details (https://dev.mysql.com/doc/refman/5.7/en/group-replication-configuring-instances.html ) - since you are using mysql shell, you can use: rebootClusterFromCompleteOutage() ( https://dev.mysql.com/doc/mysql-shell/8.0/en/reboot-outage.html ) Thank you for using MySQL