| Showing 1-30 of 32 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 75852 | 2015-02-10 20:15 | 2015-05-11 1:00 | MySQL Server: Group Replication | No Feedback (3264 days) | S3 | server:5.7.5-labs-group-replication | Linux | Any | mysql5.7.5 fail to start command-line client |
| 75939 | 2015-02-17 21:24 | 2015-09-05 1:00 | MySQL Server: Group Replication | No Feedback (3147 days) | S1 | 5.7.5-labs-group-replication | Linux (ubuntu 14.04) | Any | mysql 5.7.5 group replication failed |
| 78600 | 2015-09-28 9:44 | 2015-12-11 15:22 | MySQL Server: Group Replication | No Feedback (3049 days) | S1 | 0.5.0-dmr | Ubuntu (14.04) | Any | Compiling group replication plugin will fail because of boost_1_58_0 package |
| 88607 | 2017-11-22 14:14 | 2018-01-08 1:00 | MySQL Server: Group Replication | No Feedback (2291 days) | S1 | mysql5.7.19 | CentOS (7) | Any | mysql start group_replication Too many connections 2k+ then then mysql crash |
| 89381 | 2018-01-24 12:53 | 2018-03-08 1:00 | MySQL Server: Group Replication | No Feedback (2232 days) | S2 | 8.0.4 | Debian (9.3) | Any | Rolling upgrading Group Replication using packages |
| 92875 | 2018-10-21 19:37 | 2018-11-25 1:00 | MySQL Server: Group Replication | No Feedback (1970 days) | S2 | 8.0.11 | Debian (9) | Any | Crash after member tries to recover |
| 91933 | 2018-08-08 9:22 | 2019-03-12 1:00 | MySQL Server: Group Replication | No Feedback (1863 days) | S1 | 8.0.11 | CentOS | Any | MySQL Group Replication - Transaction hangs in COMMIT state at primary |
| 95043 | 2019-04-17 9:08 | 2019-06-04 1:00 | MySQL Server: Group Replication | No Feedback (1779 days) | S3 | 5.7.24 | Any | Any | Certification_handler does not handle the HANDLER_START_ACTION |
| 96213 | 2019-07-16 6:01 | 2019-11-26 5:14 | MySQL Server: Group Replication | No Feedback (1685 days) | S3 | Any | Any | group replication auto_increment_offset is not accurate | |
| 96244 | 2019-07-18 7:25 | 2019-12-02 14:28 | MySQL Server: Group Replication | No Feedback (1660 days) | S3 | 8.0.16 | Ubuntu (Ubuntu 18.04 in Digital Ocean) | Any | [GCS] The member was unable to join the group. Local port: 33061 |
| 97645 | 2019-11-14 16:06 | 2019-12-16 1:00 | MySQL Server: Group Replication | No Feedback (1584 days) | S3 | 8.0.18 | CentOS | Any | Cannot rejoinInstance after a group replication member being expelled |
| 97676 | 2019-11-18 9:27 | 2019-12-29 1:00 | MySQL Server: Group Replication | No Feedback (1571 days) | S3 | 5.7.27 | Any | Any | Slave SQL error 1237 warnings |
| 97800 | 2019-11-26 14:21 | 2020-01-11 1:00 | MySQL Server: Group Replication | No Feedback (1558 days) | S1 | MySQL 8.0.18 | Red Hat (7.4) | x86 | lost binlog when sync-binlog=1 in single primary group replication |
| 99975 | 2020-06-24 18:01 | 2020-07-27 1:00 | MySQL Server: Group Replication | No Feedback (1360 days) | S3 | CentOS | Any | Error_code: 1451; handler error HA_ERR_ROW_IS_REFERENCED, Error_code: MY-001451 | |
| 100103 | 2020-07-03 13:17 | 2020-08-07 1:00 | MySQL Server: Group Replication | No Feedback (1348 days) | S1 | 8.0.11 | Linux (CentOS) | Any | Slave SQL for channel 'group_replication_recovery': Could not execute Write_rows |
| 99830 | 2020-06-10 4:33 | 2020-10-30 15:54 | MySQL Server: Group Replication | No Feedback (1354 days) | S5 | 8.0.18 | Linux | x86 | Improve the performance robustness for MGR |
| 101114 | 2020-10-10 6:46 | 2020-11-15 1:00 | MySQL Server: Group Replication | No Feedback (1249 days) | S2 | 8.0.18 | Any | Any | MySQL group replication not set read_only before it joins the GR cluster |
| 101274 | 2020-10-22 11:45 | 2020-11-25 1:00 | MySQL Server: Group Replication | No Feedback (1239 days) | S2 | 8.0.22 | Any | Any | Clone Operation succeed but node failing join GR when relay logs are present |
| 103808 | 2021-05-26 4:09 | 2021-07-01 1:00 | MySQL Server: Group Replication | No Feedback (1021 days) | S3 | 8.0.22 | CentOS (CentOS Linux release 7.8.2003 (Core)) | x86 | group repl MY-013328: Certification information is too large for transmission |
| 103641 | 2021-05-10 14:50 | 2021-07-04 1:00 | MySQL Server: Group Replication | No Feedback (1018 days) | S1 | 8.0.22 | Any | Any | After the mgr primary node was killed, the data is inconsistent between nodes |
| 99745 | 2020-05-29 16:13 | 2021-07-13 5:30 | MySQL Server: Group Replication | No Feedback (1383 days) | S3 | 8.0.16 | Ubuntu (18.04) | x86 | Slave stops with HA_ERR_KEY_NOT_FOUND error |
| 104677 | 2021-08-20 12:04 | 2021-09-24 1:00 | MySQL Server: Group Replication | No Feedback (936 days) | S3 | 8.0.23 | Debian | Any | Old joiner blocked for a long time in the failure recovery(Local recovery phase) |
| 104646 | 2021-08-17 15:24 | 2021-10-01 1:00 | MySQL Server: Group Replication | No Feedback (929 days) | S2 | 8.0.26 | Debian (10.10) | x86 | InnoDB group replication stalled on large transaction and high network bandwidth |
| 105352 | 2021-10-28 6:20 | 2021-12-01 1:00 | MySQL Server: Group Replication | No Feedback (868 days) | S2 | 8.0.22 | Any | Any | Innodb Cluster can not replication user privilege when user have grant options |
| 105584 | 2021-11-16 3:19 | 2021-12-24 1:00 | MySQL Server: Group Replication | No Feedback (845 days) | S3 | 8.0.x,5.7.26 | CentOS | Any | when there are two same relay_log file name in relay_log.index, mgr can't online |
| 86149 | 2017-05-01 17:00 | 2022-01-21 2:55 | MySQL Server: Group Replication | No Feedback (2511 days) | S3 | 5.7.17 | CentOS | Any | MySQL Group Replication Crash - Failing assertion: !cursor->index->is_committed |
| 106586 | 2022-02-27 13:10 | 2022-04-02 1:00 | MySQL Server: Group Replication | No Feedback (746 days) | S3 | 8.0.23 8.0.26 | Any | Any | after flush tables function error |
| 107176 | 2022-05-02 10:24 | 2022-06-20 3:55 | MySQL Server: Group Replication | No Feedback (667 days) | S2 | 8.0.28 | Ubuntu (20.04 LTS) | Any | Dual stack ubuntu group replication setup fails on add instance |
| 112967 | 2023-11-06 1:07 | 2023-12-07 1:00 | MySQL Server: Group Replication | No Feedback (132 days) | S2 | 8.0.28 | Debian (Debian GNU/Linux 10 (buster)) | x86 | Crash when a member is immediately reconnected after disconnection |
| 113225 | 2023-11-26 22:13 | 2023-12-28 1:00 | MySQL Server: Group Replication | No Feedback (111 days) | S3 | Any | Any | Error on observer while running replication hook 'before_commit' |
| Showing 1-30 of 32 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
