Showing all 25 (Edit, Save, CSV, Feed) |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
84224 | 2016-12-16 7:16 | 2017-01-31 5:04 | MySQL Server: Group Replication | Can't repeat (2614 days) | S3 | 5.7.17-log | Linux (centos 6.6) | Any | mysql group replication bug |
84792 | 2017-02-02 12:49 | 2017-05-03 13:18 | MySQL Server: Group Replication | Can't repeat (2522 days) | S3 | 5.7.17 | Any | Any | Idle GR Cluster: Member CPU hog |
86621 | 2017-06-08 11:39 | 2017-11-15 18:03 | MySQL Server: Group Replication | Can't repeat (2326 days) | S3 | 5.7.18 | Linux (CentOS 6.6 x86_64) | Any | GCS report Warning log in a dead loop |
87235 | 2017-07-28 7:33 | 2017-09-26 14:23 | MySQL Server: Group Replication | Can't repeat (2376 days) | S2 | 5.7.19 | CentOS (Linux localhost 3.10.0-514.26.2.el7.x86_64 #1 SMP Tue Jul 4 15:04:05 UTC 2017 x86) | Any | "STOP GROUP_REPLICATION" cause deadlock |
90488 | 2018-04-18 7:02 | 2018-07-11 1:00 | MySQL Server: Group Replication | Can't repeat (2088 days) | S2 | 5.7.21 MySQL Communinity Edition | Ubuntu (16.04) | x86 | mysqld crash on "start group_replication" with bootstrap |
90534 | 2018-04-20 13:58 | 2023-09-12 10:45 | MySQL Server: Group Replication | Can't repeat (199 days) | S1 | 8.0.11, 8.0.12 | MacOS (10.12.6) | x86 | InnoDB Cluster members stop by failed start of Group Replication |
91163 | 2018-06-07 1:10 | 2018-06-22 15:31 | MySQL Server: Group Replication | Can't repeat (2107 days) | S1 | 8.0.11 | CentOS (7.4) | Any | MGR member cannnot be joined, which has more executed transactions than present |
91465 | 2018-06-28 12:20 | 2020-12-28 15:02 | MySQL Server: Group Replication | Can't repeat (2083 days) | S3 | 5.7.20-log | Linux (Red Hat 4.8.5-16) | x86 | network is ok, but GR node been unreachable |
92219 | 2018-08-29 6:48 | 2018-10-31 1:04 | MySQL Server: Group Replication | Can't repeat (1976 days) | S3 | 5.7 | Any | Any | Under RECOVERING Received_transaction_set and GTID_EXECUTED upside down |
93784 | 2019-01-02 14:17 | 2020-08-15 1:13 | MySQL Server: Group Replication | Can't repeat (1895 days) | S3 | 8.0.12 | CentOS | x86 | Commit timestamp is more recent than the immediate commit timestamp despite SYNC |
96025 | 2019-06-28 11:47 | 2020-06-04 8:22 | MySQL Server: Group Replication | Can't repeat (1730 days) | S1 | 8.0.16 | Ubuntu (18.04.2) | x86 | Missing replication recovery user after brief network outage |
96113 | 2019-07-06 16:14 | 2019-12-29 12:37 | MySQL Server: Group Replication | Can't repeat (1554 days) | S1 | 5.7.26 | Red Hat (Amazon Linux AMI 2018.03 - rhel fedora) | Other (36) | mysqld got signal 11 |
97707 | 2019-11-20 12:39 | 2023-09-12 10:49 | MySQL Server: Group Replication | Can't repeat (199 days) | S1 | all version with MGR | Any | Any | group replication lost transaction when init by ansible |
98151 | 2020-01-08 1:03 | 2023-09-12 11:14 | MySQL Server: Group Replication | Can't repeat (199 days) | S3 | 8.0.18 | Any | Any | group replication with wrong member_state after server shutdown |
98524 | 2020-02-09 2:47 | 2023-09-12 10:51 | MySQL Server: Group Replication | Can't repeat (199 days) | S3 | 8.0.19 | CentOS | x86 | ERROR 3096 (HY000): The START GROUP_REPLICATION command failed as there was an e |
100381 | 2020-07-30 15:07 | 2020-10-14 17:19 | MySQL Server: Group Replication | Can't repeat (1262 days) | S2 | 8.0.21 | CentOS (CentOS Linux release 7.7.1908 (Core)) | x86 ( Intel(R) Xeon(R) CPU E5-2640 0 @ 2.50GHz) | Group replication primary got stuck after attempting to rejoin a group member |
100881 | 2020-09-17 18:08 | 2020-09-18 10:44 | MySQL Server: Group Replication | Can't repeat (1288 days) | S2 | 8.0.17 | SUSE (15 SP01) | x86 (x86_64) | [ERROR] [MY-010584] [Repl] Error executing row event: Error_code: MY-001146 |
106430 | 2022-02-10 8:41 | 2022-02-17 14:31 | MySQL Server: Group Replication | Can't repeat (771 days) | S3 | Any (OKD) | x86 | Timeout on wait for view after joining group | |
108797 | 2022-10-17 9:00 | 2022-10-18 1:38 | MySQL Server: Group Replication | Can't repeat (528 days) | S3 | 8.0.26 | Linux (CentOS Linux release 7.6.1810) | Any | MGR Sencondary node don`t appling relay logs |
108856 | 2022-10-23 15:25 | 2022-10-25 17:04 | MySQL Server: Group Replication | Can't repeat (521 days) | S2 | 8.0.15 | CentOS | x86 | Group replication executes different transactions with same GTID |
110266 | 2023-03-03 6:40 | 2024-03-14 6:59 | MySQL Server: Group Replication | Can't repeat (388 days) | S3 | 8.0.27 | Any | Any | The secondary node of the mgr cluster has a deadlock |
110537 | 2023-03-29 4:02 | 2023-03-31 0:37 | MySQL Server: Group Replication | Can't repeat (364 days) | S1 | 5.7.40 | Any | Any | MySQL cluster fail to auto recover |
112277 | 2023-09-06 15:10 | 2023-09-10 12:34 | MySQL Server: Group Replication | Can't repeat (203 days) | S1 | 5.7.43 | Any | Any | MySQL block forever |
112368 | 2023-09-17 14:39 | 2023-09-21 2:29 | MySQL Server: Group Replication | Can't repeat (190 days) | S1 | 5.7.36 | Debian (Debian GNU/Linux 10 (buster)) | Any | Mismatched SQL for the same GTID transaction across primary and secondary |
112779 | 2023-10-20 3:57 | 2023-10-24 6:39 | MySQL Server: Group Replication | Can't repeat (157 days) | S3 | 8.0.33 | Any | Any | Not auto rejoin after failing to parse relay log |
Showing all 25 (Edit, Save, CSV, Feed) |