| Showing 1-30 of 49 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 113813 | 2024-01-31 2:26 | 2024-02-07 8:24 | MySQL Server: Replication | Verified (79 days) | S3 | MySQL8.0,8.0.36 | Any | Any | Semisync will abort due to wrong transaction binlog postion comparison |
| 113038 | 2023-11-10 7:26 | 2023-11-10 8:36 | MySQL Server: Replication | Verified (161 days) | S2 | 8.0 | Any | Any | Contribution by Tencent: mi->data_lock not release if heartbeat event mismatch |
| 113187 | 2023-11-22 16:24 | 2023-11-28 21:06 | MySQL Server: Replication | Verified (145 days) | S5 | 8.0 and above | Any | Any | replica SQL thread purge applied relay logs blocked commit on source node |
| 113202 | 2023-11-23 17:12 | 2023-11-23 21:29 | MySQL Server: Replication | Verified (148 days) | S3 | 8.0.35 | Any | Any | p_s.processlist table does not contain async replica threads after restart |
| 113229 | 2023-11-27 7:57 | 2023-11-27 11:11 | MySQL Server: Replication | Can't repeat (144 days) | S3 | 8.0.33 | Any (CentOS Linux 7) | Any | mysqld: Duplicate entry 'mysql/slave_worker_info' for key 'tablespaces.name' |
| 113489 | 2023-12-22 7:43 | 2024-01-04 3:36 | MySQL Server: Replication | Can't repeat (106 days) | S3 | 5.7.26 5.7.36 5.7.44 | Any | Any | gtid_executed table lost the last binlog gtids |
| 113539 | 2024-01-02 19:44 | 2024-02-13 1:00 | MySQL Server: Replication | No Feedback (67 days) | S3 | 5.7 | Any | Any | Binlog replication in single threaded doesn't update transactional info table |
| 113634 | 2024-01-12 17:33 | 2024-01-14 9:16 | MySQL Server: Replication | Verified (96 days) | S3 | 8.0 | Any | Any | Contribution: fix plugin semisync find minAck bug |
| 113707 | 2024-01-22 11:52 | 2024-01-22 12:04 | MySQL Server: Replication | Verified (88 days) | S3 | 8.3.0, 8.0.36 | Any | Any | replication stops after updating geometry column |
| 113727 | 2024-01-23 14:34 | 2024-01-26 6:39 | MySQL Server: Replication | Verified (84 days) | S1 | 8.0.19+ | Any | Any | GTID Replica stalls completely when log_slave_updates=0 and a local DDL executed |
| 113769 | 2024-01-26 2:42 | 2024-03-01 1:00 | MySQL Server: Replication | No Feedback (50 days) | S3 | 5.7.44 | Any | Any | Generated column json binary format is incorrent |
| 110889 | 2023-05-03 5:41 | 2023-05-03 6:07 | MySQL Server: Replication | Verified (352 days) | S5 | 8.0.32 | Any | Any | binlog rotate optimize |
| 113814 | 2024-01-31 2:42 | 2024-01-31 13:16 | MySQL Server: Replication | Verified (79 days) | S3 | MySQL8.0,5.7 | Any | Any | The Rpl_semi_sync_master_yes_tx and Rpl_semi_sync_master_no_tx are inaccurate |
| 114074 | 2024-02-21 8:35 | 2024-02-27 14:20 | MySQL Server: Replication | Verified (58 days) | S5 | 8.0.32 | Any | Any | optimize for Writeset_trx_dependency_tracker::get_dependency |
| 114198 | 2024-03-04 4:21 | 2024-03-07 7:23 | MySQL Server: Replication | Verified (44 days) | S3 | 8.0.35, 8.0.36 | Any | Any | Using PERSIST on binlog_transaction_compression partially compresses binary log |
| 114273 | 2024-03-08 2:04 | 2024-04-09 1:00 | MySQL Server: Replication | No Feedback (11 days) | S3 | MySQL8.0.22 to 8.0.33 | Any | Any | turn on the binlog compression and load large data to server will cause oom |
| 114310 | 2024-03-12 4:14 | 2024-03-19 7:24 | MySQL Server: Replication | Verified (38 days) | S3 | 8.0.33 | Any | Any | Master_compression_algorithm output is wrong |
| 114361 | 2024-03-15 1:53 | 2024-03-19 11:11 | MySQL Server: Replication | Verified (32 days) | S5 | 8.0 | Any | Any | Unaligned Delegate's lock reduces performance |
| 114472 | 2024-03-25 7:17 | 2024-03-25 7:20 | MySQL Server: Replication | Verified (25 days) | S3 | V8.0 | Any | Any | MySQL replica encounter error when master and replica innodb_strict_mode=OFF |
| 114511 | 2024-03-29 7:05 | 2024-04-02 9:58 | MySQL Server: Replication | Not a Bug (17 days) | S3 | MySQL8.0.22 | Any | Any | Turn on binlog compression and read binlog generate by big transaction cause oom |
| 114588 | 2024-04-09 1:34 | 2024-04-09 14:49 | MySQL Server: Replication | Verified (10 days) | S3 | 8.0 | Any | Any | Setting the instance to super-read-only still allows the flush priveleges comman |
| 111914 | 2023-07-28 16:38 | 2023-08-11 10:26 | MySQL Server: Replication | Verified (263 days) | S2 | 8.0.33 | Any | Any | Global replication filters replace channel specific filters |
| 110774 | 2023-04-23 13:52 | 2023-04-25 2:49 | MySQL Server: Replication | Not a Bug (360 days) | S3 | 8.0.33 | Any | Any | 'show replica status' set the field_flag of 'Second_Behind_Source' NOTNULL |
| 111027 | 2023-05-15 10:49 | 2023-10-27 17:07 | MySQL Server: Replication | Closed (193 days) | S2 | 5.7.42, 8.0.33 | Any | Any | Multi-column indexes with writest will cause HA_ERR_FOUND_DUPP_KEY |
| 111075 | 2023-05-18 13:24 | 2023-05-18 14:01 | MySQL Server: Replication | Verified (337 days) | S3 | 8.0 | Any | Any | I_S.PROCESSLIST shows misleading information for replica threads |
| 111146 | 2023-05-25 8:45 | 2024-04-10 9:40 | MySQL Server: Replication | Verified (329 days) | S3 | 8.0, 8.0.36 | Any | Any | Write set conflict two parallel-able transaction on table with foreign key |
| 111149 | 2023-05-25 9:50 | 2023-11-03 20:32 | MySQL Server: Replication | Closed (255 days) | S3 | 8.0 | Any | Any | Lock leak in heartbeat_queue_event() |
| 111242 | 2023-06-01 12:31 | 2023-06-06 16:10 | MySQL Server: Replication | Unsupported (318 days) | S2 | 5.7.41 and 8.0.33 | Any | Any | Replica Issue - ('mysql.infoschema'@'localhost') does not exist |
| 111247 | 2023-06-01 15:02 | 2023-06-05 15:39 | MySQL Server: Replication | Verified (322 days) | S3 | MySQL8.0.22, 8.0.23 | Any | Any | Executing a SELECT statement causes to allocate lots of memory for binlog |
| 111507 | 2023-06-21 5:12 | 2023-06-21 9:56 | MySQL Server: Replication | Verified (303 days) | S3 | 5.7.42 | Any | Any | Huge memory usage by write_set with foreign key info |
| Showing 1-30 of 49 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
