| « Show Previous 30 Entries | Showing 31-60 of 445 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 110889 | 2023-05-03 5:41 | 2023-05-03 6:07 | MySQL Server: Replication | Verified (358 days) | S5 | 8.0.32 | Any | Any | binlog rotate optimize |
| 110683 | 2023-04-13 13:21 | 2023-04-14 7:59 | MySQL Server: Replication | Verified (377 days) | S3 | 5.7, 8.0 | Any | Any | Multi-threaded slave statistics output is incorrect |
| 110566 | 2023-03-30 11:05 | 2023-03-31 8:20 | MySQL Server: Replication | Verified (391 days) | S2 | 5.7.41 | Any | Any | Contribution by Tencent: checkpoint may regression in mts |
| 110533 | 2023-03-28 15:49 | 2023-03-29 12:17 | MySQL Server: Replication | Verified (393 days) | S3 | 8.0.32 | Any | Any | XA COMMIT may not be recovered after a crash |
| 110430 | 2023-03-20 7:11 | 2023-03-30 2:49 | MySQL Server: Replication | Verified (394 days) | S3 | 8.0 | Any | Any | XA COMMIT may not persist GTID into undo header |
| 110127 | 2023-02-19 11:37 | 2024-01-26 6:09 | MySQL Server: Replication | Verified (428 days) | S3 | 8.0.31 | Any | Any | semi-sync master wait for ack when semi-sync replica is down & async replaces it |
| 109977 | 2023-02-08 8:05 | 2023-02-08 8:30 | MySQL Server: Replication | Verified (442 days) | S3 | 8.0.32,5.7.41 | Any | Any | Contribution by Tencent: semisync plugin may print a negative server id |
| 109946 | 2023-02-06 15:51 | 2023-02-07 8:14 | MySQL Server: Replication | Verified (443 days) | S3 | 8.0 | Any | Any | Contribution: doc: Add docs for COM_BINLOG_DUMP_GTID |
| 109829 | 2023-01-29 9:52 | 2023-01-30 15:35 | MySQL Server: Replication | Verified (451 days) | S3 | all | Any | Any | Bug of function minAck in semisync plugin lead to unexpected behavior |
| 109530 | 2023-01-04 9:42 | 2023-01-05 11:02 | MySQL Server: Replication | Verified (476 days) | S3 | 8.0.30, 8.0.31 | Any | Any | Fail to write drop temp table binlog event in semi sync mode |
| 109397 | 2022-12-15 15:20 | 2022-12-16 5:47 | MySQL Server: Replication | Verified (496 days) | S3 | 8.0 | Any | Any | Contribution: Fix typo in a comment: timestamps => sequences |
| 109290 | 2022-12-06 8:28 | 2023-01-13 6:20 | MySQL Server: Replication | Verified (468 days) | S5 | 5.7.39 | Ubuntu | x86 | WRITESET causing performance issue for replication on a replica |
| 109268 | 2022-12-02 6:00 | 2022-12-06 4:45 | MySQL Server: Replication | Verified (506 days) | S3 | 8.0 | Any | Any | binlog file record unused "use `database`" along with actually query |
| 109217 | 2022-11-28 9:51 | 2022-12-12 3:19 | MySQL Server: Replication | Verified (500 days) | S2 | 5.7.40 | Any | Any | The datas of master and standby are inconsistent for Spatial Data Formats |
| 109031 | 2022-11-09 2:47 | 2022-11-30 9:00 | MySQL Server: Replication | Verified (513 days) | S3 | 5.7.38 | Any | Any | 'start slave' reports error after stopping slave during IO thd reconnecting |
| 109023 | 2022-11-08 4:24 | 2022-11-08 7:51 | MySQL Server: Replication | Verified (534 days) | S3 | 5.7,8.0.31 | Any | Any | Leak REPL_SLAVE_ACL privilege error is ambiguous |
| 109016 | 2022-11-07 11:51 | 2022-11-08 15:57 | MySQL Server: Replication | Verified (534 days) | S3 | 5.7.38 | Any | Any | Slave crashed when master restart |
| 108682 | 2022-10-04 19:32 | 2022-10-09 12:48 | MySQL Server: Replication | Verified (567 days) | S2 | 5.7.39 | Any | Any | Read-Committed Isolation, UPDATES wrapped in DROP TEMPORARY TABLE IF EXISTS |
| 108537 | 2022-09-19 13:29 | 2022-09-20 15:46 | MySQL Server: Replication | Verified (584 days) | S2 | 5.7 | Any | Any | gtid_subset should reset null_value to false |
| 108514 | 2022-09-16 1:10 | 2022-09-16 5:53 | MySQL Server: Replication | Verified (587 days) | S2 | 8.0.21 | Any | Any | Return value of Gtid_set::ensure_sidno(int) not get checked |
| 108510 | 2022-09-16 0:31 | 2022-09-16 5:36 | MySQL Server: Replication | Verified (587 days) | S2 | 8.0.21 | Any | Any | Return value of rotate() not get checked |
| 108405 | 2022-09-06 16:22 | 2022-09-07 4:56 | MySQL Server: Replication | Verified (596 days) | S3 | 8.0 | Any | Any | Contribution: Implement logic to be able to get a consistent GTID |
| 108061 | 2022-08-03 11:33 | 2022-08-04 2:01 | MySQL Server: Replication | Verified (630 days) | S3 | 5.7.39 | Any | Any | Contribution by Tencent: Generated column calculate error without base column |
| 107991 | 2022-07-27 2:02 | 2023-10-23 8:31 | MySQL Server: Replication | Verified (185 days) | S2 | 8.0.25 | Any | Any | Clone_persist_gtid causes memory leak |
| 107928 | 2022-07-20 23:09 | 2022-07-26 2:17 | MySQL Server: Replication | Verified (644 days) | S2 | 8.0 | Any | Any | MySQL 8.0 Replication breaks when tmpdir space is filled |
| 107677 | 2022-06-28 7:41 | 2022-06-28 8:18 | MySQL Server: Replication | Verified (667 days) | S2 | 8.0.29, 5.7.38 | Any | Any | Contribution by Tencent: create table like temporary table missing charset info |
| 107438 | 2022-05-31 19:57 | 2023-05-02 16:49 | MySQL Server: Replication | Verified (694 days) | S2 | 5.7.38 | CentOS (8) | Any | JSON STORED generated column values are inserted as NULL on replica |
| 107371 | 2022-05-23 11:12 | 2022-05-23 12:29 | MySQL Server: Replication | Verified (703 days) | S3 | Ver 8.0, 5.7 | Any | Any | slave error: Slave I/O for channel '': Unexpected master's heartbeat data |
| 107293 | 2022-05-15 13:34 | 2022-05-21 20:52 | MySQL Server: Replication | Verified (705 days) | S2 | 5.7.37, 8.0.28 | Any | Any | CURRENT_TIMESTAMP not safe after all? |
| 107113 | 2022-04-24 10:53 | 2022-04-26 4:17 | MySQL Server: Replication | Verified (732 days) | S3 | 5.7,8.0, 8.0.28 | Any | Any | Got fatal error 1236 from master when reading data from binary log |
| « Show Previous 30 Entries | Showing 31-60 of 445 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
