| Showing 1-30 of 49 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 109530 | 2023-01-04 9:42 | 2023-01-05 11:02 | MySQL Server: Replication | Verified (84 days) | S3 | 8.0.30, 8.0.31 | Any | Any | Fail to write drop temp table binlog event in semi sync mode |
| 106942 | 2022-04-07 10:44 | 2022-04-19 9:40 | MySQL Server: Replication | Not a Bug (345 days) | S3 | 8.0.28 | Any | Any | alter user may lead replication broken with error 1396 |
| 108892 | 2022-10-27 1:47 | 2022-10-31 3:32 | MySQL Server: Replication | Can't repeat (150 days) | S3 | 8.0.26 | CentOS (CentOS Linux release 7.6.1810) | Any | MGR Sencondary node don`t appling relay logs |
| 108948 | 2022-11-01 7:50 | 2022-11-21 11:16 | MySQL Server: Replication | Unsupported (129 days) | S3 | 5.6 | Windows | Any | Getting mislead error message after successful replication set |
| 109016 | 2022-11-07 11:51 | 2022-11-08 15:57 | MySQL Server: Replication | Verified (142 days) | S3 | 5.7.38 | Any | Any | Slave crashed when master restart |
| 109023 | 2022-11-08 4:24 | 2022-11-08 7:51 | MySQL Server: Replication | Verified (142 days) | S3 | 5.7,8.0.31 | Any | Any | Leak REPL_SLAVE_ACL privilege error is ambiguous |
| 109031 | 2022-11-09 2:47 | 2022-11-30 9:00 | MySQL Server: Replication | Verified (121 days) | S3 | 5.7.38 | Any | Any | 'start slave' reports error after stopping slave during IO thd reconnecting |
| 109154 | 2022-11-21 14:52 | 2023-01-27 17:19 | MySQL Server: Replication | Closed (62 days) | S3 | 8.0 | Any | Any | Contribution: Fix incorrect suggested commands to start slave in error logs ... |
| 109217 | 2022-11-28 9:51 | 2022-12-12 3:19 | MySQL Server: Replication | Verified (108 days) | S2 | 5.7.40 | Any | Any | The datas of master and standby are inconsistent for Spatial Data Formats |
| 109268 | 2022-12-02 6:00 | 2022-12-06 4:45 | MySQL Server: Replication | Verified (114 days) | S3 | 8.0 | Any | Any | binlog file record unused "use `database`" along with actually query |
| 109397 | 2022-12-15 15:20 | 2022-12-16 5:47 | MySQL Server: Replication | Verified (104 days) | S3 | 8.0 | Any | Any | Contribution: Fix typo in a comment: timestamps => sequences |
| 109485 | 2022-12-27 0:34 | 2023-01-25 13:53 | MySQL Server: Replication | Closed (64 days) | S2 | 5.7.40 | Any | Any | Contribution by Tencent: Previous_gtids miss gtid when binlog_order_commits off |
| 108834 | 2022-10-20 11:05 | 2022-11-04 14:14 | MySQL Server: Replication | Not a Bug (146 days) | S3 | all version | Any | Any | MySQL Online DDL add AUTO_INCREMENT |
| 109620 | 2023-01-13 10:11 | 2023-01-19 15:19 | MySQL Server: Replication | Duplicate (70 days) | S3 | 5.7.38, 5.7.39, 5.7.40 | Red Hat | Any | Slave_skip_errors not skipping the error 1399 on MySQL 5.7.38,5.7.39,5.7.40 |
| 109829 | 2023-01-29 9:52 | 2023-01-30 15:35 | MySQL Server: Replication | Verified (59 days) | S3 | all | Any | Any | Bug of function minAck in semisync plugin lead to unexpected behavior |
| 109857 | 2023-01-31 8:55 | 2023-02-03 4:54 | MySQL Server: Replication | Duplicate (55 days) | S2 | 5.7.38 | Any | Any | Truncate table with foreign key crash replication. |
| 109946 | 2023-02-06 15:51 | 2023-02-07 8:14 | MySQL Server: Replication | Verified (51 days) | S3 | 8.0 | Any | Any | Contribution: doc: Add docs for COM_BINLOG_DUMP_GTID |
| 109977 | 2023-02-08 8:05 | 2023-02-08 8:30 | MySQL Server: Replication | Verified (50 days) | S3 | 8.0.32,5.7.41 | Any | Any | Contribution by Tencent: semisync plugin may print a negative server id |
| 110094 | 2023-02-16 7:34 | 2023-02-22 13:55 | MySQL Server: Replication | Can't repeat (36 days) | S2 | 8.0.25 | Any | Any | When slave replays the STOP EVENT, the stop slave will cause a dead cycle |
| 110127 | 2023-02-19 11:37 | 2023-02-23 9:35 | MySQL Server: Replication | Verified (36 days) | S3 | 8.0.31 | Any | Any | semi-sync master wait for ack when semi-sync replica is down & async replaces it |
| 110151 | 2023-02-21 9:30 | 2023-02-21 16:55 | MySQL Server: Replication | Duplicate (37 days) | S3 | 5.7.38, 5.7.39, 5.7.40 | Red Hat | Any | Slave_skip_errors not skipping the error 1399 on MySQL 5.7.38,5.7.39,5.7.40 |
| 110430 | 2023-03-20 7:11 | 2023-03-30 2:49 | MySQL Server: Replication | Verified (2 days) | S3 | 8.0 | Any | Any | XA COMMIT may not persist GTID into undo header |
| 110533 | 2023-03-28 15:49 | 2023-03-29 12:17 | MySQL Server: Replication | Verified (1 day) | S3 | 8.0.32 | Any | Any | XA COMMIT may not be recovered after a crash |
| 110566 | 2023-03-30 11:05 | 2023-03-30 11:27 | MySQL Server: Replication | Analyzing | S2 | 5.7.41 | Any | Any | Contribution by Tencent: checkpoint may regression in mts |
| 108061 | 2022-08-03 11:33 | 2022-08-04 2:01 | MySQL Server: Replication | Verified (238 days) | S3 | 5.7.39 | Any | Any | Contribution by Tencent: Generated column calculate error without base column |
| 107008 | 2022-04-13 11:44 | 2022-05-05 7:11 | MySQL Server: Replication | Verified (329 days) | S2 | 5.7.37 | Any | Any | Contribution by Tencent:Shutdown hang due to work thread wait for ack |
| 107113 | 2022-04-24 10:53 | 2022-04-26 4:17 | MySQL Server: Replication | Verified (340 days) | S3 | 5.7,8.0, 8.0.28 | Any | Any | Got fatal error 1236 from master when reading data from binary log |
| 107293 | 2022-05-15 13:34 | 2022-05-21 20:52 | MySQL Server: Replication | Verified (313 days) | S2 | 5.7.37, 8.0.28 | Any | Any | CURRENT_TIMESTAMP not safe after all? |
| 107366 | 2022-05-23 1:53 | 2023-03-30 8:09 | MySQL Server: Replication | Closed (86 days) | S2 | 8.0.18 and prior, 8.0.29, 8.0.30, 8.0.31, 8.0.32 | Any | Any | Contribution by Tencent: Invalid JSON value, Error_code: 3903 |
| 107371 | 2022-05-23 11:12 | 2022-05-23 12:29 | MySQL Server: Replication | Verified (311 days) | S3 | Ver 8.0, 5.7 | Any | Any | slave error: Slave I/O for channel '': Unexpected master's heartbeat data |
| Showing 1-30 of 49 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
