Showing all 30 (Edit, Save, CSV, Feed) |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
99679 | 2020-05-25 2:32 | 2020-05-26 9:14 | MySQL Server | Can't repeat (1428 days) | S3 | 8.0.18 | Any | Any | stop group_replication will assert |
107862 | 2022-07-13 10:29 | 2022-07-14 10:26 | MySQL Server: Clone Plugin | Verified (650 days) | S3 | 8.0.25 | Any | Any | clone failed when table with special name |
86900 | 2017-07-03 6:51 | 2017-07-04 7:33 | MySQL Server: DML | Not a Bug (2485 days) | S3 | 5.7.13 | Any | Any | load data result mismatch when escaped by character is 't' |
104096 | 2021-06-24 0:44 | 2021-11-02 20:55 | MySQL Server: Group Replication | Closed (903 days) | S3 | 8.0.25, 8.0.26 | Any | Any | set gtid_next may block query |
101635 | 2020-11-17 6:29 | 2020-11-24 9:29 | MySQL Server: Group Replication | Verified (1246 days) | S3 | 8.0.21, 8.0.22 | Any | Any | group_replication_local_address port overflow |
101237 | 2020-10-20 8:38 | 2020-10-27 7:37 | MySQL Server: Group Replication | Verified (1274 days) | S3 | 8.0.21 | Any | Any | stop group_replicaiton may block long time when restart server |
100906 | 2020-09-22 8:38 | 2020-10-30 11:12 | MySQL Server: Group Replication | Not a Bug (1271 days) | S2 | 8.0.18, 8.0.21 | Any | Any | cannot execute read-only transaction when group_replication in ERROR state |
100299 | 2020-07-23 2:57 | 2022-02-24 11:12 | MySQL Server: Group Replication | Closed (789 days) | S2 | 8.0.18, 8.0.21 | Any | Any | secondly role cannot join to group_replication after fail-over |
100163 | 2020-07-09 0:56 | 2022-01-12 21:40 | MySQL Server: Group Replication | Closed (832 days) | S2 | 8.0.18 | Any | Any | xa commit failed when stop group_replication will lead node error |
104690 | 2021-08-23 10:47 | 2021-08-25 0:30 | MySQL Server: Group Replication | Verified (972 days) | S3 | 8.0.25, 8.0.26 | Any | Any | transaction cannot commit in AFTER consistencty mode when have unreachable node |
100052 | 2020-07-01 0:45 | 2020-07-20 8:59 | MySQL Server: Group Replication | Not a Bug (1373 days) | S3 | 8.0.18, 8.0.20 | Any | Any | install group_replication will write error log |
99689 | 2020-05-26 4:02 | 2023-09-12 10:54 | MySQL Server: Group Replication | Not a Bug (224 days) | S3 | 8.0.18 | Any | Any | member cannot add to group_replication cluster after failover |
98643 | 2020-02-18 8:11 | 2020-05-12 15:07 | MySQL Server: Group Replication | Closed (1442 days) | S3 | 8.0.18 | Any | Any | group replication will be block primary node shutdown |
98473 | 2020-02-04 4:18 | 2020-03-02 10:18 | MySQL Server: Group Replication | Not a Bug (1513 days) | S3 | 8.0.18 | Any | Any | group replication will be block after lock table |
110446 | 2023-03-21 3:16 | 2023-03-21 8:43 | MySQL Server: Group Replication | Verified (399 days) | S3 | 8.0.32 | Any | Any | main.kill_myisam will assert when install group_replication |
98151 | 2020-01-08 1:03 | 2023-09-12 11:14 | MySQL Server: Group Replication | Can't repeat (224 days) | S3 | 8.0.18 | Any | Any | group replication with wrong member_state after server shutdown |
99638 | 2020-05-20 0:53 | 2020-12-04 12:54 | MySQL Server: InnoDB storage engine | Closed (1237 days) | S5 | 8.0.18 | Any | Any | xa transaction with low performance |
110485 | 2023-03-24 5:00 | 2023-03-27 5:12 | MySQL Server: InnoDB storage engine | Verified (396 days) | S3 | 8.0.32 | Any | Any | FLUSH TABLE FOR EXPORT will lead deadlock |
100028 | 2020-06-29 8:06 | 2020-07-07 11:08 | MySQL Server: Optimizer | Verified (1394 days) | S3 | 8.0.18, 5.6.48, 5.7.30,8.0.20 | Any | Any | LIKE behavior is not same |
101469 | 2020-11-05 4:53 | 2020-11-05 10:38 | MySQL Server: Options | Verified (1265 days) | S3 | 8.0.21, 8.0.22, 5.7.32 | Any | Any | skip_name_resolve does not take effect |
101310 | 2020-10-26 4:39 | 2020-10-27 22:55 | MySQL Server: Partitions | Verified (1275 days) | S3 | 8.0.21, 8.0.22 | Any | Any | partition by key distribute unbalance for utf8 |
113115 | 2023-11-17 2:20 | 2023-12-27 8:04 | MySQL Server: Replication | Can't repeat (118 days) | S3 | 5.7.21 | SUSE | Any | semi-sync slave exit checksum error and master exit with net_flush error |
113116 | 2023-11-17 2:29 | 2023-11-17 23:23 | MySQL Server: Replication | Duplicate (158 days) | S3 | 5.7.21 | SUSE | Any | master binlog_dump exit and then semi-sync slave report checksum error |
93978 | 2019-01-18 9:44 | 2019-01-22 14:04 | MySQL Server: Replication | Not a Bug (1918 days) | S3 | 5.7.23 | Any | Any | XA COMMIT success with same xid |
93809 | 2019-01-04 2:55 | 2019-02-16 1:00 | MySQL Server: Replication | No Feedback (1894 days) | S3 | 5.7.24 | Any | Any | lost a whole file's gtid |
102661 | 2021-02-19 11:20 | 2021-02-19 12:17 | MySQL Server: XA transactions | Verified (1159 days) | S3 | 8.0.22, 8.0.23, 5.7.33 | Any | Any | xa prepare failed lead replication error |
100156 | 2020-07-08 10:30 | 2020-07-08 15:21 | MySQL Server: XA transactions | Duplicate (1385 days) | S3 | 8.0.18, 8.0.20 | Any | Any | XA COMMIT still work after stop group_replication |
99205 | 2020-04-08 1:36 | 2020-04-08 11:19 | MySQL Server: XA transactions | Verified (1476 days) | S2 | 8.0.18, 8.0.19 | Any | Any | xa prepare write binlog while execute failed |
98288 | 2020-01-20 0:57 | 2020-02-13 8:23 | MySQL Server: XA transactions | Duplicate (1531 days) | S3 | 5.7.26 | Any | Any | xa commit crash lead mysql replication error |
94130 | 2019-01-30 7:22 | 2019-04-12 18:39 | MySQL Server: XA transactions | Closed (1838 days) | S3 | 5.7.23 | Any | Any | XA COMMIT may lead replication broken |
Showing all 30 (Edit, Save, CSV, Feed) |