| Showing 1-30 of 50 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 109031 | 2022-11-09 2:47 | 2022-11-30 9:00 | MySQL Server: Replication | Verified (113 days) | S3 | 5.7.38 | Any | Any | 'start slave' reports error after stopping slave during IO thd reconnecting |
| 108234 | 2022-08-23 7:00 | 2022-10-03 12:29 | MySQL Server: Replication | Can't repeat (170 days) | S3 | mysql 8.0.28 | Any | Any | A Document incorrect regarding Replication with Differing Table Definitions |
| 106942 | 2022-04-07 10:44 | 2022-04-19 9:40 | MySQL Server: Replication | Not a Bug (337 days) | S3 | 8.0.28 | Any | Any | alter user may lead replication broken with error 1396 |
| 109268 | 2022-12-02 6:00 | 2022-12-06 4:45 | MySQL Server: Replication | Verified (106 days) | S3 | 8.0 | Any | Any | binlog file record unused "use `database`" along with actually query |
| 109829 | 2023-01-29 9:52 | 2023-01-30 15:35 | MySQL Server: Replication | Verified (51 days) | S3 | all | Any | Any | Bug of function minAck in semisync plugin lead to unexpected behavior |
| 108876 | 2022-10-25 23:00 | 2022-10-27 17:22 | MySQL Server: Replication | Can't repeat (146 days) | S2 | 8.0.28 | CentOS ( 7.9.2009) | x86 | CLONE operation results in mysqld server hang on startup |
| 106999 | 2022-04-13 8:44 | 2022-04-14 12:02 | MySQL Server: Replication | Can't repeat (342 days) | S2 | 5.7.37 | Any | Any | contributed by Tencent: shutdown hang due to binlog dump stick at wait_new_event |
| 107677 | 2022-06-28 7:41 | 2022-06-28 8:18 | MySQL Server: Replication | Verified (267 days) | S2 | 8.0.29, 5.7.38 | Any | Any | Contribution by Tencent: create table like temporary table missing charset info |
| 108061 | 2022-08-03 11:33 | 2022-08-04 2:01 | MySQL Server: Replication | Verified (230 days) | S3 | 5.7.39 | Any | Any | Contribution by Tencent: Generated column calculate error without base column |
| 107366 | 2022-05-23 1:53 | 2023-01-03 13:10 | MySQL Server: Replication | Closed (78 days) | S2 | 8.0.18 and prior, 8.0.29 | Any | Any | Contribution by Tencent: Invalid JSON value, Error_code: 3903 |
| 109485 | 2022-12-27 0:34 | 2023-01-25 13:53 | MySQL Server: Replication | Closed (56 days) | S2 | 5.7.40 | Any | Any | Contribution by Tencent: Previous_gtids miss gtid when binlog_order_commits off |
| 109977 | 2023-02-08 8:05 | 2023-02-08 8:30 | MySQL Server: Replication | Verified (42 days) | S3 | 8.0.32,5.7.41 | Any | Any | Contribution by Tencent: semisync plugin may print a negative server id |
| 106875 | 2022-03-30 14:43 | 2022-04-05 14:13 | MySQL Server: Replication | Verified (351 days) | S3 | 8.0.28 | Any | Any | Contribution by Tencent: writeset can not be used when binlog_format is mixed |
| 107996 | 2022-07-27 6:38 | 2023-02-22 18:29 | MySQL Server: Replication | Closed (28 days) | S3 | 8.0.29 | Any | Any | Contribution by Tencent: wrong default value of geometry column |
| 107008 | 2022-04-13 11:44 | 2022-05-05 7:11 | MySQL Server: Replication | Verified (321 days) | S2 | 5.7.37 | Any | Any | Contribution by Tencent:Shutdown hang due to work thread wait for ack |
| 109946 | 2023-02-06 15:51 | 2023-02-07 8:14 | MySQL Server: Replication | Verified (43 days) | S3 | 8.0 | Any | Any | Contribution: doc: Add docs for COM_BINLOG_DUMP_GTID |
| 109154 | 2022-11-21 14:52 | 2023-01-27 17:19 | MySQL Server: Replication | Closed (54 days) | S3 | 8.0 | Any | Any | Contribution: Fix incorrect suggested commands to start slave in error logs ... |
| 109397 | 2022-12-15 15:20 | 2022-12-16 5:47 | MySQL Server: Replication | Verified (96 days) | S3 | 8.0 | Any | Any | Contribution: Fix typo in a comment: timestamps => sequences |
| 108405 | 2022-09-06 16:22 | 2022-09-07 4:56 | MySQL Server: Replication | Verified (196 days) | S3 | 8.0 | Any | Any | Contribution: Implement logic to be able to get a consistent GTID |
| 107293 | 2022-05-15 13:34 | 2022-05-21 20:52 | MySQL Server: Replication | Verified (305 days) | S2 | 5.7.37, 8.0.28 | Any | Any | CURRENT_TIMESTAMP not safe after all? |
| 107884 | 2022-07-14 17:16 | 2022-08-17 1:00 | MySQL Server: Replication | No Feedback (218 days) | S3 | 8.0.29 | Any | Any | Error message after stop semi sync replication |
| 109530 | 2023-01-04 9:42 | 2023-01-05 11:02 | MySQL Server: Replication | Verified (76 days) | S3 | 8.0.30, 8.0.31 | Any | Any | Fail to write drop temp table binlog event in semi sync mode |
| 108948 | 2022-11-01 7:50 | 2022-11-21 11:16 | MySQL Server: Replication | Unsupported (121 days) | S3 | 5.6 | Windows | Any | Getting mislead error message after successful replication set |
| 107113 | 2022-04-24 10:53 | 2022-04-26 4:17 | MySQL Server: Replication | Verified (332 days) | S3 | 5.7,8.0, 8.0.28 | Any | Any | Got fatal error 1236 from master when reading data from binary log |
| 108537 | 2022-09-19 13:29 | 2022-09-20 15:46 | MySQL Server: Replication | Verified (184 days) | S2 | 5.7 | Any | Any | gtid_subset should reset null_value to false |
| 107438 | 2022-05-31 19:57 | 2022-06-07 9:38 | MySQL Server: Replication | Verified (294 days) | S2 | 5.7.38 | CentOS (8) | Any | JSON STORED generated column values are inserted as NULL on replica |
| 109023 | 2022-11-08 4:24 | 2022-11-08 7:51 | MySQL Server: Replication | Verified (134 days) | S3 | 5.7,8.0.31 | Any | Any | Leak REPL_SLAVE_ACL privilege error is ambiguous |
| 108104 | 2022-08-10 3:06 | 2022-08-10 12:39 | MySQL Server: Replication | Not a Bug (224 days) | S5 | MySQL5.7.26 | Any | Any | LOCK_status affect transaction performance when do a "show status" command |
| 108892 | 2022-10-27 1:47 | 2022-10-31 3:32 | MySQL Server: Replication | Can't repeat (142 days) | S3 | 8.0.26 | CentOS (CentOS Linux release 7.6.1810) | Any | MGR Sencondary node don`t appling relay logs |
| 107574 | 2022-06-15 21:07 | 2022-12-28 16:00 | MySQL Server: Replication | Closed (84 days) | S2 | 5.7.38, 5.7.40 | Any | Any | MTR deadlocks when preserving commit order and changing read_only. |
| Showing 1-30 of 50 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
