Showing all 18 (Edit, Save, CSV, Feed) |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
86259 | 2017-05-10 6:45 | 2017-07-14 23:26 | MySQL Router | Closed (2470 days) | S2 | 2.1.3 | Oracle Linux | Any | Router reconnect time too long |
86261 | 2017-05-10 6:53 | 2018-01-10 2:11 | MySQL Router | Closed (2290 days) | S3 | 2.1.3 | Oracle Linux | Any | Read-only connect fails if there are no read-only nodes |
86760 | 2017-06-20 17:38 | 2017-10-27 11:42 | Shell AdminAPI InnoDB Cluster / ReplicaSet | Closed (2365 days) | S3 | 1.0.9 | Any | Any | MySQL Shell: dba.dropMetaDataSchema() doesn't work. |
86797 | 2017-06-22 16:16 | 2017-07-27 17:06 | Shell AdminAPI InnoDB Cluster / ReplicaSet | Verified (2457 days) | S1 | 5.7.18 | Linux | Any | InnoDB Cluster does not report when nodes fall behind or stop writing data. |
86828 | 2017-06-26 17:09 | 2017-08-20 18:56 | Shell AdminAPI InnoDB Cluster / ReplicaSet | Duplicate (2453 days) | S3 | 1.0.9 | Linux | Any | MySQL Shell SSL WRONG_VERSION_NUMBER ERROR |
92053 | 2018-08-17 8:55 | 2019-06-05 15:19 | MySQL Server: Documentation | Closed (1779 days) | S3 | 5.7 | Any | Any | Document Bug for Production Deployment of InnoDB Cluster |
92219 | 2018-08-29 6:48 | 2018-10-31 1:04 | MySQL Server: Group Replication | Can't repeat (1996 days) | S3 | 5.7 | Any | Any | Under RECOVERING Received_transaction_set and GTID_EXECUTED upside down |
90468 | 2018-04-17 9:30 | 2018-05-09 11:18 | Shell General / Core Client | Analyzing (2171 days) | S3 | 1.0.11,8.0.4 | Red Hat (7.4) | x86 | "Access denied" when execute cluster.forceQuorumUsingPartitionOf |
96721 | 2019-09-02 20:00 | 2019-09-22 19:24 | Shell AdminAPI InnoDB Cluster / ReplicaSet | Verified (1670 days) | S2 | 8.0.15 | CentOS (7) | x86 (x86_64) | Add or remove instances to InnoDB cluster fails in mult-primary mode |
99345 | 2020-04-24 9:03 | 2020-05-13 9:50 | MySQL Server: Group Replication | Closed (1436 days) | S2 | 8.0.19 | Oracle Linux (Official Docker Image : mysql/mysql-server:8.0.19) | x86 | Group replication consistency error when add instance BUG#30394258 not fixed |
105352 | 2021-10-28 6:20 | 2021-12-01 1:00 | MySQL Server: Group Replication | No Feedback (870 days) | S2 | 8.0.22 | Any | Any | Innodb Cluster can not replication user privilege when user have grant options |
106937 | 2022-04-06 23:43 | 2023-10-10 15:52 | Shell AdminAPI InnoDB Cluster / ReplicaSet | Closed (706 days) | S2 | 8.0.28 | CentOS | x86 | Emergency Failover after Network Split Invalidates Primary in ClusterSet |
107696 | 2022-06-29 5:41 | 2022-06-29 13:05 | Shell AdminAPI InnoDB Cluster / ReplicaSet | Not a Bug (659 days) | S3 | 8.29 | CentOS | Any | MySQL innoDB cluster user account with host IP |
108067 | 2022-08-03 23:25 | 2022-08-04 11:04 | Shell General / Core Client | Not a Bug (623 days) | S3 | 8.0.29 | Ubuntu (Ubuntu 18.04.5 LTS) | x86 | mysql executable does not respect MYSQL_PWD env variable in an InnoDB Cluster |
108856 | 2022-10-23 15:25 | 2022-10-25 17:04 | MySQL Server: Group Replication | Can't repeat (541 days) | S2 | 8.0.15 | CentOS | x86 | Group replication executes different transactions with same GTID |
112368 | 2023-09-17 14:39 | 2023-09-21 2:29 | MySQL Server: Group Replication | Can't repeat (210 days) | S1 | 5.7.36 | Debian (Debian GNU/Linux 10 (buster)) | Any | Mismatched SQL for the same GTID transaction across primary and secondary |
112888 | 2023-10-30 21:35 | 2023-10-31 1:42 | MySQL Server: Group Replication | Closed (170 days) | S3 | 8.0.27 | Any | Any | View_change_log_event's in secondary cluster break cross-DC failovers |
114286 | 2024-03-08 18:15 | 2024-04-09 18:49 | MySQL Server | Can't repeat (9 days) | S1 | 8.0.36 | Debian (12) | x86 | Using Clone Recovery for addInstance on MySQL Innodb Cluster uses 100% Memory |
Showing all 18 (Edit, Save, CSV, Feed) |