| Showing all 26 (Edit, Save, CSV, Feed) |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 117660 | 2025-03-11 4:23 | 2025-12-21 20:45 | MySQL Server: Replication | Duplicate (81 days) | S2 | 8.4.2 | Oracle Linux (8.10) | x86 | MySQL 8.4.2: InnoDB Assertion Failure on ha_innodb.cc:11675 Due to strlen(m_remote_path) != 0 After Promoting Replica |
| 117782 | 2025-03-25 2:54 | 2025-03-25 9:42 | MySQL Server: Replication | Won't fix (350 days) | S3 | 5.7.44 | Any | Any | Semi-synchronous replication causes significant performance degradation |
| 118040 | 2025-04-23 11:35 | 2025-04-23 13:00 | MySQL Server: Replication | Verified (321 days) | S5 | 8.0 | Any | Any | Reduce Redundant init_and_set_log_file_name Calls |
| 118116 | 2025-05-05 17:41 | 2025-06-20 1:00 | MySQL Server: Replication | No Feedback (264 days) | S1 | 8.0.41 | Any | Any | HA_ERR_CORRUPT_EVENT on replication from datetime -> datetime(6) |
| 118168 | 2025-05-12 12:27 | 2025-09-02 7:14 | MySQL Server: Replication | Verified (301 days) | S1 | 8.0.41 | Any | Any | MySQL data dictionary fails to upgrade at startup with lock timeout on ALTER TABLE |
| 118210 | 2025-05-16 10:15 | 2025-05-18 16:43 | MySQL Server: Replication | Verified (296 days) | S3 | 8.0.42 | Any | Any | Invisible Index Binlog Replay Bugfix |
| 118322 | 2025-06-01 4:47 | 2025-12-07 20:45 | MySQL Server: Replication | No Feedback (234 days) | S2 | 8.0.20 | Any | x86 | Result of `show master status` is not correct !!! |
| 118356 | 2025-06-04 11:58 | 2025-07-13 10:29 | MySQL Server: Replication | Verified (272 days) | S2 | 8.0.42, 8.4.5 9.3.0 | Any | Any | MySQL attempts committing transaction not fitting on disk, then crashes. |
| 118412 | 2025-06-10 23:24 | 2025-07-01 9:18 | MySQL Server: Replication | Verified (252 days) | S3 | 8.0.41, 8.0.42 | Any | Any | DML succeeds on Semi-sync without Replicas if Source is stopped |
| 118462 | 2025-06-17 2:56 | 2025-07-01 14:09 | MySQL Server: Replication | Can't repeat (252 days) | S3 | 8.0.39 | Red Hat (Rocky Linux 8.10) | x86 (AMD EPYC 7R32) | Executed SQL on replica is different from source |
| 118602 | 2025-07-08 10:26 | 2025-08-19 0:07 | MySQL Server: Replication | Can't repeat (203 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 (198 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 (215 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 (214 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 (150 days) | S3 | Any | Any | Purge Relaylog Leads To Semi-sync Increased Response even set relay_log_space_limit=0 | |
| 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 | 2025-10-30 16:03 | 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 (125 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 (98 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 (84 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 (32 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 |
| 119996 | 2026-03-06 11:07 | 2026-03-06 11:07 | MySQL Server: Replication | Open | S2 | 9.6 | Any | Any | Row delete from a table with selfreferental FK breaks replication |
| Showing all 26 (Edit, Save, CSV, Feed) |
