| Showing all 29 (Edit, Save, CSV, Feed) |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 118602 | 2025-07-08 10:26 | 2025-08-19 0:07 | MySQL Server: Replication | Can't repeat (305 days) | S2 | 8.0.42 | Ubuntu (8.0.42-0ubuntu0.24.04.1) | x86 | SQL Thread cannot be stopped when last error was 1755 |
| 118700 | 2025-07-22 12:55 | 2025-12-07 20:45 | MySQL Server: Replication | No Feedback (300 days) | S2 | 8.0.40 | Any | Any | Due to the master enabling the NO_BACKSLASH_ESCAPES sql_mode, an error occurs during replay on the slave. |
| 118797 | 2025-08-07 2:08 | 2025-12-18 6:35 | MySQL Server: Replication | Verified (317 days) | S2 | 8.4, 8.4.6, 9.4.0 | Any | Any | Contribution by Tencent: previous gtids may loss xa commit/rollback gtids |
| 118798 | 2025-08-07 9:22 | 2025-08-08 7:36 | MySQL Server: Replication | Verified (316 days) | S1 | 8.0.40 | Ubuntu | Any | Replication Break in 8.0.40 salve when from 8.0.33 Master |
| 119091 | 2025-09-29 9:56 | 2025-12-07 20:45 | MySQL Server: Replication | Duplicate (252 days) | S3 | Any | Any | Purge Relaylog Leads To Semi-sync Increased Response even set relay_log_space_limit=0 | |
| 119253 | 2025-10-28 4:57 | 2026-05-28 1:13 | MySQL Server: Replication | Documenting (75 days) | S3 | 9.7.0-er | Any | Any | innodb.tablespace_encrypt_9 crashing the server with assertion failure |
| 119256 | 2025-10-28 7:12 | 2025-10-28 7:12 | MySQL Server: Replication | Open | S2 | 8.0.43 | Any | Any | Replication with additional column on source can cause data loss and should not be allowed |
| 119270 | 2025-10-30 9:12 | 2026-04-14 8:43 | MySQL Server: Replication | Open | S3 | MySQL8.0,5.7 | Any | Any | Single-statement transactions can cause latency spikes on the replica |
| 119304 | 2025-11-05 2:08 | 2026-01-15 10:31 | MySQL Server: Replication | Open (227 days) | S3 | 5.7，8.0 | Any | Any | SQL_LOAD-xxxx file exists when the SQL thread checks permissions, causing the SQL thread fail to start |
| 119312 | 2025-11-05 17:30 | 2026-01-13 11:33 | MySQL Server: Replication | Open | S3 | 8.4.x | Any | Any | `start replica` command adds an invalid record to mysql.slave_master_info |
| 119489 | 2025-12-02 4:44 | 2025-12-02 4:46 | MySQL Server: Replication | Open (200 days) | S3 | 8.4.7 | Any | Any | GTID tags can violate restrictions |
| 119558 | 2025-12-16 8:39 | 2025-12-16 8:57 | MySQL Server: Replication | Open (186 days) | S3 | 8.4.7 | Any | Any | SHOW BINLOG EVENTS fails with Event too big |
| 119676 | 2026-01-14 6:26 | 2026-01-14 13:11 | MySQL Server: Replication | Open | S2 | 8.0.44 | Any | Any | Column statistic (histograms) is not replicated in read_only replica mode |
| 119855 | 2026-02-06 18:36 | 2026-02-06 18:38 | MySQL Server: Replication | Open (134 days) | S3 | 8.0 | Any | Any | Relay Log Recovery after mts_recovery_groups failure should be retried |
| 119947 | 2026-02-26 9:19 | 2026-02-26 9:30 | MySQL Server: Replication | Open | S2 | 8.0.45 | Any | Any | ordered_commit some transactions had flush errors, but committed successfully.resulting in master-slave inconsistency |
| 119957 | 2026-02-28 7:28 | 2026-02-28 7:28 | MySQL Server: Replication | Open | S2 | 8.0 | Any | Any | Contribution by Tencent: Replica Crash Due to Stale fts_doc_id in HASH_SCAN Replication Path |
| 120115 | 2026-03-19 15:21 | 2026-03-19 15:32 | MySQL Server: Replication | Open | S3 | 8.4 | Any | Any | CHANGE REPLICATION FILTER REPLICATE_IGNORE_DB with ROW BASED REPLICATION NOT WORKING AS DESCRIBED |
| 120128 | 2026-03-23 8:14 | 2026-05-28 1:13 | MySQL Server: Replication | Documenting (73 days) | S3 | 8.0.* | Any | Any | When explicit_defaults_for_timestamp is off, inserting a null value causes replication exceptions. |
| 120135 | 2026-03-24 2:02 | 2026-03-31 6:50 | MySQL Server: Replication | Duplicate (81 days) | S3 | 8.0.* | Any | Any | When explicit_defaults_for_timestamp is off, replication exceptions when insert a null value. |
| 120177 | 2026-03-30 6:38 | 2026-04-01 12:10 | MySQL Server: Replication | Open | S3 | 5.7.44 | Any | Any | Lost gtids after crash recovery |
| 120181 | 2026-03-30 21:14 | 2026-04-20 13:09 | MySQL Server: Replication | Open | S3 | Any | Any | Contribution: Fix stale sql_mode values in Query_event Doxygen documentatio ... | |
| 120198 | 2026-04-01 7:45 | 2026-04-16 14:30 | MySQL Server: Replication | Verified (65 days) | S3 | 8.0.45 | Any | Any | Lost gtid after crash recovery |
| 120238 | 2026-04-09 9:16 | 2026-04-09 9:34 | MySQL Server: Replication | Open | S3 | 5.7 8.0 | Linux | Any | maybe cause "could not find next log" if rotate binary log without fsync @@log_bin_index's parent dir |
| 120266 | 2026-04-14 9:12 | 2026-04-14 9:12 | MySQL Server: Replication | Open | S3 | MySQL 8.4 | Any | Any | Replication delay when SQL thread skips large already-executed transactions |
| 120278 | 2026-04-17 2:44 | 2026-05-12 2:31 | MySQL Server: Replication | Open (39 days) | S2 | 8.0.44 8.4.9 | Any | Any | mts_event_coord_cmp() uses strcmp() for binlog filename comparison, causing incorrect ordering when binlog index exceeds |
| 120281 | 2026-04-17 9:21 | 2026-04-17 11:32 | MySQL Server: Replication | Open (64 days) | S2 | 8.0.42 | Linux (any) | Any | replica_preserve_commit_order causes infinite deadlock in group commit pipeline, blocking all application writes |
| 120327 | 2026-04-23 7:46 | 2026-04-23 12:40 | MySQL Server: Replication | Open | S2 | MySQL 8.4 | Any | Any | Unsigned integer wraparound in Binlog_sender::run() when binlog_row_event_max_size is set to a large value |
| 120471 | 2026-05-14 0:08 | 2026-05-18 9:15 | MySQL Server: Replication | Open (37 days) | S1 | 8.0.43, 8.0.46, 8.4.9, 9.7.0 | Any (reproduced on macOS and Linux) | Any | binary log violates read after write (commit) consistency |
| 120480 | 2026-05-14 20:59 | 2026-06-12 21:18 | MySQL Server: Replication | Open (8 days) | S3 | 8.0.40 | Any | Any | Crash in set_and_validate_user_attributes during relay log recovery |
| Showing all 29 (Edit, Save, CSV, Feed) |
