Showing 1–30 of 43
ID# Date Updated Type Status Sev Version OS CPU Summary
1193042025-11-05
2:08		2026-01-15
10:31		MySQL Server: ReplicationOpen
(364 days)		S35.7，8.0AnyAnySQL_LOAD-xxxx file exists when the SQL thread checks permissions, causing the SQL thread fail to start
1193122025-11-05
17:30		2026-01-13
11:33		MySQL Server: ReplicationOpenS38.4.xAnyAny`start replica` command adds an invalid record to mysql.slave_master_info
1194892025-12-02
4:44		2025-12-02
4:46		MySQL Server: ReplicationOpen
(337 days)		S38.4.7AnyAnyGTID tags can violate restrictions
1195582025-12-16
8:39		2025-12-16
8:57		MySQL Server: ReplicationOpen
(323 days)		S38.4.7AnyAnySHOW BINLOG EVENTS fails with Event too big
1196762026-01-14
6:26		2026-01-14
13:11		MySQL Server: ReplicationOpenS28.0.44AnyAnyColumn statistic (histograms) is not replicated in read_only replica mode
1198552026-02-06
18:36		2026-02-06
18:38		MySQL Server: ReplicationOpen
(271 days)		S38.0AnyAnyRelay Log Recovery after mts_recovery_groups failure should be retried
1199472026-02-26
9:19		2026-02-26
9:30		MySQL Server: ReplicationOpenS28.0.45AnyAnyordered_commit some transactions had flush errors, but committed successfully.resulting in master-slave inconsistency
1199572026-02-28
7:28		2026-02-28
7:28		MySQL Server: ReplicationOpenS28.0AnyAnyContribution by Tencent: Replica Crash Due to Stale fts_doc_id in HASH_SCAN Replication Path
1201152026-03-19
15:21		2026-03-19
15:32		MySQL Server: ReplicationOpenS38.4AnyAnyCHANGE REPLICATION FILTER REPLICATE_IGNORE_DB with ROW BASED REPLICATION NOT WORKING AS DESCRIBED
1201282026-03-23
8:14		2026-07-23
17:09		MySQL Server: ReplicationClosed
(104 days)		S38.0.*AnyAnyWhen explicit_defaults_for_timestamp is off, inserting a null value causes replication exceptions.
1201352026-03-24
2:02		2026-03-31
6:50		MySQL Server: ReplicationDuplicate
(218 days)		S38.0.*AnyAnyWhen explicit_defaults_for_timestamp is off, replication exceptions when insert a null value.
1201772026-03-30
6:38		2026-04-01
12:10		MySQL Server: ReplicationOpenS35.7.44AnyAnyLost gtids after crash recovery
1201812026-03-30
21:14		2026-04-20
13:09		MySQL Server: ReplicationOpenS3AnyAnyContribution: Fix stale sql_mode values in Query_event Doxygen documentatio ...
1201982026-04-01
7:45		2026-04-16
14:30		MySQL Server: ReplicationVerified
(202 days)		S38.0.45AnyAnyLost gtid after crash recovery
1202382026-04-09
9:16		2026-04-09
9:34		MySQL Server: ReplicationOpenS35.7 8.0LinuxAnymaybe cause "could not find next log" if rotate binary log without fsync @@log_bin_index's parent dir
1202662026-04-14
9:12		2026-04-14
9:12		MySQL Server: ReplicationOpenS3MySQL 8.4AnyAnyReplication delay when SQL thread skips large already-executed transactions
1202782026-04-17
2:44		2026-05-12
2:31		MySQL Server: ReplicationOpen
(176 days)		S28.0.44 8.4.9AnyAnymts_event_coord_cmp() uses strcmp() for binlog filename comparison, causing incorrect ordering when binlog index exceeds
1202812026-04-17
9:21		2026-04-17
11:32		MySQL Server: ReplicationOpen
(201 days)		S28.0.42Linux (any)Anyreplica_preserve_commit_order causes infinite deadlock in group commit pipeline, blocking all application writes
1203272026-04-23
7:46		2026-04-23
12:40		MySQL Server: ReplicationOpenS2MySQL 8.4AnyAnyUnsigned integer wraparound in Binlog_sender::run() when binlog_row_event_max_size is set to a large value
1204712026-05-14
0:08		2026-10-14
9:16		MySQL Server: ReplicationNot a Bug
(21 days)		S18.0.43, 8.0.46, 8.4.9, 9.7.0Any (reproduced on macOS and Linux)Anybinary log violates read after write (commit) consistency
1204802026-05-14
20:59		2026-06-12
21:18		MySQL Server: ReplicationOpen
(145 days)		S38.0.40AnyAnyCrash in set_and_validate_user_attributes during relay log recovery
1207382026-06-22
10:55		2026-10-07
14:18		MySQL Server: ReplicationDuplicate
(28 days)		S15.7.25Linux (6)x86Corruption of the index file caused stale binary log entries to be re-applied after executing FLUSH LOGS
1207392026-06-22
11:42		2026-10-07
14:17		MySQL Server: ReplicationNeed Feedback
(28 days)		S15.7.25Linuxx86Corruption of the index file caused stale binary log entries to be re-applied after executing FLUSH LOGS
1207572026-06-24
6:04		2026-09-17
16:47		MySQL Server: ReplicationClosed
(48 days)		S28.4AnyAny"Start Transaction" modifier in the binary log cannot be replayed on an instance that does not have binary logs enabled.
1207742026-06-25
12:16		2026-06-25
12:16		MySQL Server: ReplicationOpenS28.4.8LinuxAnyreplication worker thread dealock
1207772026-06-25
19:24		2026-06-26
6:29		MySQL Server: ReplicationVerified
(131 days)		S38.4.9, 9.7.0LinuxAnyReplica crash on short Format_description_event post_header_len
1210352026-07-30
8:50		2026-07-30
8:54		MySQL Server: ReplicationOpen
(97 days)		S58.0.46+, 8.4.10+Linuxx86Extra Table_map events are included in the binary log
1210502026-08-03
22:09		2026-10-22
14:48		MySQL Server: ReplicationDocumenting
(27 days)		S38.0, 8.4, 9.7 and 26.7AnyAnyConfusing Last_IO_Error "fatal error 1236" since 8.0 (also affecting 8.4, 9.7 and 26.7) and more.
1210562026-08-04
22:19		2026-10-22
14:48		MySQL Server: ReplicationDocumenting
(27 days)		S28.0, 8.4, 9.7 and 26.7.0AnyAnyThe recovery recommendations in Last_IO_Error "fatal error 1236" are wrong (since 8.0.17).
1213142026-09-18
10:03		2026-09-30
14:48		MySQL Server: ReplicationDocumenting
(44 days)		S28.0.40/5.7.44AnyAnyMTS recovery silently skips transactions, leaving holes in gtid_executed
Showing 1–30 of 43

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.031 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.