| Showing all 7 (Edit, Save, CSV, Feed) |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 97266 | 2019-10-17 2:39 | 2022-08-29 3:34 | MySQL Server: Group Replication | Verified (2087 days) | S1 | 5.7.28 | CentOS (aliyun ECS CentOS 7.4) | x86 | GR fail to start,conflict with k8s CNI(flannel) |
| 102556 | 2021-02-10 15:48 | 2021-04-06 12:18 | MySQL Server: Group Replication | Verified (1558 days) | S2 | 8.0.21 | CentOS (Release: 7.7.1908) | x86 (Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz) | Apparent deadlock involving group replication applier threads |
| 106032 | 2022-01-04 14:17 | 2022-01-21 6:47 | MySQL Server: Group Replication | Verified (1269 days) | S3 | 8.0.27 Community Server | Debian (11.2) | x86 (HyperV) | MySQL uses up ram/swap after short member disconnect within innodb cluster |
| 109668 | 2023-01-17 21:56 | 2024-11-05 2:50 | MySQL Server: Group Replication | Verified (761 days) | S2 | 8.0.27, 8.0.33 | CentOS | x86 | XCom connection stalled forever in read() syscall over network |
| 114624 | 2024-04-11 13:37 | 2024-10-14 13:16 | MySQL Server: Group Replication | Verified (271 days) | S2 | 8.0.39 | Ubuntu (22.04) | x86 | Deadlock on primary replica when adding instance to replica cluster with writes |
| 116532 | 2024-11-03 3:07 | 2024-11-28 14:36 | MySQL Server: Group Replication | Verified (226 days) | S1 | 8.0.40 | Ubuntu (24.04) | x86 (x86-64) | Group Replication cluster deployed across a regional GCP regularly got stuck |
| 118216 | 2025-05-16 14:13 | 2025-05-19 14:14 | MySQL Server: Group Replication | Verified (54 days) | S4 | 8.0.40 | Any (5.14.0-503.29.1.el9_5.x86_64) | x86 | read replica gives error for "select group_replication_get_write_concurrency();" |
| Showing all 7 (Edit, Save, CSV, Feed) |
