| Showing all 28 (Edit, Save, CSV, Feed) |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 79499 | 2015-12-03 2:25 | 2015-12-22 12:07 | MySQL Server: Group Replication | Closed (3041 days) | S3 | 0.6 | Any | Any | MySQL crash when xcom of Group Replication assign the same port as that of DB |
| 80241 | 2016-02-02 19:35 | 2016-08-02 19:31 | MySQL Server: Group Replication | Closed (2817 days) | S3 | 0.7.0-labs | CentOS (el7-x86-64bit) | Any | Starting group replication causes MySQL to crash with sig 6 with selinux |
| 84224 | 2016-12-16 7:16 | 2017-01-31 5:04 | MySQL Server: Group Replication | Can't repeat (2635 days) | S3 | 5.7.17-log | Linux (centos 6.6) | Any | mysql group replication bug |
| 84574 | 2017-01-20 0:39 | 2017-02-09 12:53 | MySQL Server: Group Replication | Not a Bug (2626 days) | S2 | 5.7.17 | Any | Any | In Group Replication, DDL execute on partitioned node leads to split brain |
| 84631 | 2017-01-24 1:38 | 2019-01-03 11:45 | MySQL Server: Documentation | Closed (1933 days) | S3 | 5.7 | Any | Any | Group Replication Installation Documentation |
| 85221 | 2017-02-28 8:51 | 2017-07-11 11:44 | MySQL Server: Packaging | Closed (2474 days) | S3 | 5.7.17 | Red Hat | Any | Group Replication : Error while adding instance in group. |
| 87295 | 2017-08-03 8:16 | 2017-08-03 13:25 | Tests: Group Replication | Verified (2451 days) | S3 | 8.0.2 | Any | Any | Test group_replication.gr_single_primary_majority_loss_1 produces warnings |
| 89058 | 2017-12-26 12:15 | 2017-12-29 11:25 | MySQL Server: Group Replication | Not a Bug (2303 days) | S3 | 5.7.20 | Linux | Any | Group Replication(MGR) ERROR while executing concurrent DDL and DML |
| 89686 | 2018-02-16 7:47 | 2019-04-30 11:04 | MySQL Server: Documentation | Closed (1816 days) | S3 | 5.7, 8.0 | Any | Any | Need to add "offset is provided by server_id and increment is 7" to GR manual. |
| 92219 | 2018-08-29 6:48 | 2018-10-31 1:04 | MySQL Server: Group Replication | Can't repeat (1997 days) | S3 | 5.7 | Any | Any | Under RECOVERING Received_transaction_set and GTID_EXECUTED upside down |
| 92932 | 2018-10-24 17:15 | 2018-12-06 1:00 | MySQL Server | No Feedback (1962 days) | S3 | 5.7.24 | Ubuntu (16.04.3 LTS (Xenial Xerus)) | x86 | Group Replication plugin doesn't load in MySQL 5.7.24 |
| 93784 | 2019-01-02 14:17 | 2020-08-15 1:13 | MySQL Server: Group Replication | Can't repeat (1916 days) | S3 | 8.0.12 | CentOS | x86 | Commit timestamp is more recent than the immediate commit timestamp despite SYNC |
| 96244 | 2019-07-18 7:25 | 2019-12-02 14:28 | MySQL Server: Group Replication | No Feedback (1663 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 |
| 97293 | 2019-10-18 16:51 | 2019-11-20 16:46 | MySQL Server: Group Replication | Not a Bug (1612 days) | S2 | at least 8.0.16, 8.0.17 & 8.0.18 | Ubuntu (Ubuntu 18.04.2 LTS) | x86 (GNU/Linux 4.15.0 x86_64) | group replication plugin memory leak |
| 97450 | 2019-10-31 22:24 | 2019-12-26 11:54 | MySQL Package Repos | Can't repeat (1576 days) | S2 | 5.7.28 | Ubuntu (18.06) | x86 | Got an error reading communication packets MySQL docker overlay network |
| 97800 | 2019-11-26 14:21 | 2020-01-11 1:00 | MySQL Server: Group Replication | No Feedback (1561 days) | S1 | MySQL 8.0.18 | Red Hat (7.4) | x86 | lost binlog when sync-binlog=1 in single primary group replication |
| 98151 | 2020-01-08 1:03 | 2023-09-12 11:14 | MySQL Server: Group Replication | Can't repeat (220 days) | S3 | 8.0.18 | Any | Any | group replication with wrong member_state after server shutdown |
| 98473 | 2020-02-04 4:18 | 2020-03-02 10:18 | MySQL Server: Group Replication | Not a Bug (1509 days) | S3 | 8.0.18 | Any | Any | group replication will be block after lock table |
| 100221 | 2020-07-14 21:13 | 2020-08-13 1:32 | MySQL Server: Group Replication | Not a Bug (1345 days) | S2 | 8.0 | Ubuntu | x86 | MySQL Group Replication between hosts running containers not working |
| 101274 | 2020-10-22 11:45 | 2020-11-25 1:00 | MySQL Server: Group Replication | No Feedback (1242 days) | S2 | 8.0.22 | Any | Any | Clone Operation succeed but node failing join GR when relay logs are present |
| 105584 | 2021-11-16 3:19 | 2021-12-24 1:00 | MySQL Server: Group Replication | No Feedback (848 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 |
| 105776 | 2021-12-02 16:12 | 2022-03-06 19:30 | MySQL Server: Group Replication | Closed (775 days) | S3 | 8.0.26 | Any | Any | Simplify or automate the GR recovery user management |
| 106430 | 2022-02-10 8:41 | 2022-02-17 14:31 | MySQL Server: Group Replication | Can't repeat (792 days) | S3 | Any (OKD) | x86 | Timeout on wait for view after joining group | |
| 108821 | 2022-10-19 10:01 | 2022-11-16 13:46 | MySQL Server: Documentation | Closed (520 days) | S3 | 8.0.31 | Any | Any | DOC issue with group_replication_communication_debug_options description |
| 108856 | 2022-10-23 15:25 | 2022-10-25 17:04 | MySQL Server: Group Replication | Can't repeat (542 days) | S2 | 8.0.15 | CentOS | x86 | Group replication executes different transactions with same GTID |
| 112542 | 2023-09-27 16:20 | 2024-01-15 14:20 | MySQL Server: Group Replication | Verified (188 days) | S3 | 8.0.33 | Debian | Any | MySQL GR does not see tables with GIPK if show_gipk is OFF |
| 113089 | 2023-11-15 13:07 | 2023-12-04 10:40 | MySQL Server: Group Replication | Closed (137 days) | S1 | 8.0.23 | Linux (#84~18.04.1) | x86 | Transaction inconsistency in Group Replication with AFTER mode |
| 113838 | 2024-01-31 19:24 | 2024-02-14 0:27 | MySQL Server: Group Replication | Closed (65 days) | S3 | 8.0+ | Any | Any | Async connection failover prevents failed Group Replication member rejoin |
| Showing all 28 (Edit, Save, CSV, Feed) |
