Showing 1-30 of 49 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
113539 | 2024-01-02 19:44 | 2024-02-13 1:00 | MySQL Server: Replication | No Feedback (45 days) | S3 | 5.7 | Any | Any | Binlog replication in single threaded doesn't update transactional info table |
110683 | 2023-04-13 13:21 | 2023-04-14 7:59 | MySQL Server: Replication | Verified (349 days) | S3 | 5.7, 8.0 | Any | Any | Multi-threaded slave statistics output is incorrect |
111686 | 2023-07-07 1:57 | 2023-07-07 6:34 | MySQL Server: Replication | Verified (265 days) | S5 | 5.7,8.0, 5.7.42 | Any | Any | Contribution by Tencent: shutdown takes at least 8 seconds if have slave |
113116 | 2023-11-17 2:29 | 2023-11-17 23:23 | MySQL Server: Replication | Duplicate (132 days) | S3 | 5.7.21 | SUSE | Any | master binlog_dump exit and then semi-sync slave report checksum error |
113115 | 2023-11-17 2:20 | 2023-12-27 8:04 | MySQL Server: Replication | Can't repeat (92 days) | S3 | 5.7.21 | SUSE | Any | semi-sync slave exit checksum error and master exit with net_flush error |
114117 | 2024-02-26 10:13 | 2024-03-21 6:20 | MySQL Server: Replication | Unsupported (7 days) | S3 | 5.7.24 | CentOS (7.8) | x86 (Intel(R) Xeon(R),2 cpu,2.5GHZ,) | Slave Abnormally stoped out of io thread error:Unknown error noted |
113489 | 2023-12-22 7:43 | 2024-01-04 3:36 | MySQL Server: Replication | Can't repeat (84 days) | S3 | 5.7.26 5.7.36 5.7.44 | Any | Any | gtid_executed table lost the last binlog gtids |
110566 | 2023-03-30 11:05 | 2023-03-31 8:20 | MySQL Server: Replication | Verified (363 days) | S2 | 5.7.41 | Any | Any | Contribution by Tencent: checkpoint may regression in mts |
111242 | 2023-06-01 12:31 | 2023-06-06 16:10 | MySQL Server: Replication | Unsupported (296 days) | S2 | 5.7.41 and 8.0.33 | Any | Any | Replica Issue - ('mysql.infoschema'@'localhost') does not exist |
111507 | 2023-06-21 5:12 | 2023-06-21 9:56 | MySQL Server: Replication | Verified (281 days) | S3 | 5.7.42 | Any | Any | Huge memory usage by write_set with foreign key info |
111027 | 2023-05-15 10:49 | 2023-10-27 17:07 | MySQL Server: Replication | Closed (171 days) | S2 | 5.7.42, 8.0.33 | Any | Any | Multi-column indexes with writest will cause HA_ERR_FOUND_DUPP_KEY |
113769 | 2024-01-26 2:42 | 2024-03-01 1:00 | MySQL Server: Replication | No Feedback (28 days) | S3 | 5.7.44 | Any | Any | Generated column json binary format is incorrent |
113038 | 2023-11-10 7:26 | 2023-11-10 8:36 | MySQL Server: Replication | Verified (139 days) | S2 | 8.0 | Any | Any | Contribution by Tencent: mi->data_lock not release if heartbeat event mismatch |
114361 | 2024-03-15 1:53 | 2024-03-19 11:11 | MySQL Server: Replication | Verified (10 days) | S5 | 8.0 | Any | Any | Unaligned Delegate's lock reduces performance |
113634 | 2024-01-12 17:33 | 2024-01-14 9:16 | MySQL Server: Replication | Verified (74 days) | S3 | 8.0 | Any | Any | Contribution: fix plugin semisync find minAck bug |
112189 | 2023-08-26 23:41 | 2023-08-28 9:58 | MySQL Server: Replication | Verified (213 days) | S3 | 8.0 | Any | Any | Binlog::EventHeader position overflow |
111075 | 2023-05-18 13:24 | 2023-05-18 14:01 | MySQL Server: Replication | Verified (315 days) | S3 | 8.0 | Any | Any | I_S.PROCESSLIST shows misleading information for replica threads |
111146 | 2023-05-25 8:45 | 2023-05-26 9:28 | MySQL Server: Replication | Verified (307 days) | S3 | 8.0 | 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 (233 days) | S3 | 8.0 | Any | Any | Lock leak in heartbeat_queue_event() |
113187 | 2023-11-22 16:24 | 2023-11-28 21:06 | MySQL Server: Replication | Verified (123 days) | S5 | 8.0 and above | Any | Any | replica SQL thread purge applied relay logs blocked commit on source node |
113727 | 2024-01-23 14:34 | 2024-01-26 6:39 | MySQL Server: Replication | Verified (62 days) | S1 | 8.0.19+ | Any | Any | GTID Replica stalls completely when log_slave_updates=0 and a local DDL executed |
112030 | 2023-08-10 9:44 | 2023-08-18 14:38 | MySQL Server: Replication | Closed (223 days) | S2 | 8.0.22 | Linux (CentOS Linux 7 (Core)) | Other (3.10.0-1160.62.1.el7.x86_64 #1 SMP Tue Apr 5 16:57:59 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux) | MySQL 8.0.22 Bug Report: Inconsistent Replication to Multi-Channel Slave (No Err |
112002 | 2023-08-09 6:08 | 2023-08-09 6:24 | MySQL Server: Replication | Verified (232 days) | S3 | 8.0.23+ | Any | Any | opt_replication_sender_observe_commit_only is not honored for XA ROLLBACK |
112256 | 2023-09-05 8:00 | 2023-10-07 13:28 | MySQL Server: Replication | Verified (203 days) | S3 | 8.0.30 and above, 8.0.34 | Any | Any | The event thread_id of source changed after write to local |
114074 | 2024-02-21 8:35 | 2024-02-27 14:20 | MySQL Server: Replication | Verified (36 days) | S5 | 8.0.32 | Any | Any | optimize for Writeset_trx_dependency_tracker::get_dependency |
111540 | 2023-06-23 3:41 | 2023-06-23 5:15 | MySQL Server: Replication | Verified (279 days) | S5 | 8.0.32 | Any | Any | binlog compress optimize |
110889 | 2023-05-03 5:41 | 2023-05-03 6:07 | MySQL Server: Replication | Verified (330 days) | S5 | 8.0.32 | Any | Any | binlog rotate optimize |
113663 | 2024-01-17 11:37 | 2024-01-17 12:04 | MySQL Server: Replication | Can't repeat (71 days) | S3 | 8.0.32 | CentOS | x86 | Crash occurs when applying binlog_transaction_dependency_tracking to slave node. |
112673 | 2023-10-10 6:43 | 2023-11-11 1:00 | MySQL Server: Replication | No Feedback (139 days) | S3 | 8.0.32 | CentOS | x86 | dump from slave with --dump-slave or --dump-replica option will change binlog |
111914 | 2023-07-28 16:38 | 2023-08-11 10:26 | MySQL Server: Replication | Verified (241 days) | S2 | 8.0.33 | Any | Any | Global replication filters replace channel specific filters |
Showing 1-30 of 49 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |