Showing 1-30 of 298 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
109620 | 2023-01-13 10:11 | 2024-01-14 11:38 | MySQL Server: Replication | Duplicate (79 days) | S3 | 5.7.38, 5.7.39, 5.7.40 | Red Hat | Any | Slave_skip_errors not skipping the error 1399 on MySQL 5.7.38,5.7.39,5.7.40 |
113116 | 2023-11-17 2:29 | 2023-11-17 23:23 | MySQL Server: Replication | Duplicate (133 days) | S3 | 5.7.21 | SUSE | Any | master binlog_dump exit and then semi-sync slave report checksum error |
112979 | 2023-11-06 22:10 | 2023-11-08 0:33 | MySQL Server: Replication | Duplicate (143 days) | S3 | 8.0.35 | Any | Any | binlog_transaction_compression_level_zstd bug not fixed in 8.0.35 |
110151 | 2023-02-21 9:30 | 2023-02-21 16:55 | MySQL Server: Replication | Duplicate (402 days) | S3 | 5.7.38, 5.7.39, 5.7.40 | Red Hat | Any | Slave_skip_errors not skipping the error 1399 on MySQL 5.7.38,5.7.39,5.7.40 |
109857 | 2023-01-31 8:55 | 2023-02-03 4:54 | MySQL Server: Replication | Duplicate (420 days) | S2 | 5.7.38 | Any | Any | Truncate table with foreign key crash replication. |
106536 | 2022-02-22 8:30 | 2022-02-23 20:21 | MySQL Server: Replication | Duplicate (765 days) | S2 | 8.0.25 | Any (rhel-7.4) | Any (x86-64) | io_thread of slave db reports error when a big trx in binlog needs to be skipped |
105258 | 2021-10-19 6:34 | 2021-11-03 13:02 | MySQL Server: Replication | Duplicate (877 days) | S3 | 8.0, 8.0.26 | Any | Any | Table_map_event can not be parsed correctly if table name has mbchar and its len |
104838 | 2021-09-06 9:33 | 2021-09-06 9:39 | MySQL Server: Replication | Duplicate (935 days) | S3 | 8.21.4 | Any | Any | mysql binlog can't deserialize |
89247 | 2018-01-15 14:39 | 2021-09-01 13:10 | MySQL Server: Replication | Duplicate (940 days) | S2 | 8.0.3, 5.7.20 | Any | Any | Deadlock with MTS when slave_preserve_commit_order = ON. |
104665 | 2021-08-19 12:44 | 2021-08-19 13:16 | MySQL Server: Replication | Duplicate (953 days) | S3 | 5.7, 5.6 | Any | Any | DOTs in relay_log and log-bin breaks replication |
103595 | 2021-05-06 2:17 | 2021-06-09 9:32 | MySQL Server: Replication | Duplicate (1024 days) | S2 | 8.0.18,8.0.24 | Linux | Any | using zstd and zlib compression algorithm,master dump thread always be killed |
98678 | 2020-02-20 7:29 | 2021-05-29 5:51 | MySQL Server: Replication | Duplicate (1035 days) | S3 | 8.0.18, 8.0.19 | Linux | Any | Grant db privileges error |
95418 | 2019-05-20 4:48 | 2021-05-05 15:39 | MySQL Server: Replication | Duplicate (1059 days) | S3 | 5.6.28, 5.7.18 | Any | Any | Large transactions cause "heartbeat is not compatible with local info" on slave |
102988 | 2021-03-15 19:19 | 2021-03-16 0:30 | MySQL Server: Replication | Duplicate (1109 days) | S2 | 8.0.23, 5.7.33 | Any | Any | mysqlbinlog pipe mysql breaks with GTIDs and rpl filters because ts defaults. |
99440 | 2020-05-05 7:16 | 2020-12-03 13:37 | MySQL Server: Replication | Duplicate (1212 days) | S2 | 5.7.26 | Linux | x86 | Threads of MTS Slave randomly stuck |
101795 | 2020-11-30 7:03 | 2022-03-24 10:46 | MySQL Server: Replication | Duplicate (1212 days) | S1 | 5.7.29-32 | CentOS (7.8) | x86 | slave io_thread error,Relay log write failure: could not queue event from master |
100189 | 2020-07-12 7:11 | 2020-07-13 5:40 | MySQL Server: Replication | Duplicate (1355 days) | S3 | 5.7, 8.0 | Any | Any | Allow cleanup of gtid_executed, gtid_purged on a master, live |
100190 | 2020-07-12 7:13 | 2022-04-07 14:14 | MySQL Server: Replication | Duplicate (1355 days) | S3 | 5.7, 8.0 | Any | Any | Allow cleanup of gtid_executed, gtid_purged on a master, live |
98702 | 2020-02-21 6:36 | 2020-02-21 6:54 | MySQL Server: Replication | Duplicate (1498 days) | S3 | 8.0 | Any | Any | grant grant option statements are binlogged wrongly |
97985 | 2019-12-13 13:59 | 2019-12-30 6:49 | MySQL Server: Replication | Duplicate (1551 days) | S2 | 5.7.x 5.5.x | Any | Any | create table like temporary table creates different charset on master and slave |
93395 | 2018-11-29 6:50 | 2019-07-30 7:34 | MySQL Server: Replication | Duplicate (1704 days) | S2 | 5.7.24 | Any | Any | ALTER USER succeeds on master but fails on slave. |
81164 | 2016-04-20 20:55 | 2019-06-28 11:06 | MySQL Server: Replication | Duplicate (1736 days) | S2 | 5.6.24 | Any | Any | slave start time is very high when using milli second heartbeat time period |
94319 | 2019-02-14 2:29 | 2019-06-25 16:01 | MySQL Server: Replication | Duplicate (1739 days) | S3 | 8.0.15 | Any | Any | Format_description_log_event::write can cause segfaults |
83713 | 2016-11-07 7:48 | 2019-05-30 6:53 | MySQL Server: Replication | Duplicate (1765 days) | S3 | 5.6.31 | Any | Any | Slave failed to initialize relay log info after OS crash when use MTS and GTID |
94991 | 2019-04-11 23:43 | 2019-04-17 18:25 | MySQL Server: Replication | Duplicate (1808 days) | S3 | 5.7.25, 8.0.15 | Any | Any | multi-table deletes with foreign keys take down all replicas |
94730 | 2019-03-21 3:35 | 2019-03-26 7:00 | MySQL Server: Replication | Duplicate (1830 days) | S3 | 5.7 | Any | Any | Kill slave may cause start slave to report an error. |
94664 | 2019-03-15 3:24 | 2019-03-21 0:37 | MySQL Server: Replication | Duplicate (1835 days) | S2 | 5.7.24 | Any | Any | Binlog related deadlock leads to all incoming connection choked. |
94035 | 2019-01-24 11:41 | 2019-01-24 12:30 | MySQL Server: Replication | Duplicate (1891 days) | S2 | 5.7.24 | Any | Any | Last_Errno: 1064 and Slave_SQL_Running status is No |
93843 | 2019-01-07 17:21 | 2019-01-14 9:24 | MySQL Server: Replication | Duplicate (1905 days) | S2 | 5.7.24 | Any | Any | Setting MASTER_DELAY to 0 on a stopped delayed slave wipes the relay-log. |
93783 | 2019-01-02 13:50 | 2022-06-16 12:22 | MySQL Server: Replication | Duplicate (1912 days) | S2 | 5.7.22 | Linux (debian 9) | x86 | Incomplete statement from binary log file |
Showing 1-30 of 298 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |