| Showing 1-30 of 55 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 101722 | 2020-11-23 15:26 | 2020-11-23 16:58 | MySQL Server: Replication | Verified (57 days) | S3 | Any | Any | Contribution: Use mmap for binlog | |
| 99806 | 2020-06-08 16:30 | 2020-07-02 2:41 | MySQL Server: Replication | Verified (225 days) | S3 | Any | Any | replace master/slave terminology with primary/replica | |
| 100591 | 2020-08-20 17:57 | 2020-08-20 19:45 | MySQL Server: Replication | Verified (152 days) | S3 | Any | Any | Contribution: Bug #100586 Assertion failure `m_status == DA_ERROR` in `Diag ... | |
| 99497 | 2020-05-09 12:35 | 2020-05-11 5:34 | MySQL Server: Replication | Not a Bug (253 days) | S3 | Ubuntu | Any | Replication with SSL keep return error code 2026 | |
| 98719 | 2020-02-24 5:45 | 2020-02-24 12:26 | MySQL Server: Replication | Verified (330 days) | S3 | 5.6, 5.7, 5.7.29, 5.6.47 | Any | Any | Parallel CREATE TABLE statement binlogged in a wrong order |
| 100076 | 2020-07-02 8:03 | 2020-07-03 7:02 | MySQL Server: Replication | Verified (200 days) | S3 | 5.6, 5.7, 5.7.30, 8.0.20 | Any | Any | Missing db name when alter current db -break slave |
| 100612 | 2020-08-23 11:28 | 2020-08-24 4:49 | MySQL Server: Replication | Verified (148 days) | S3 | 5.6,5.7,8.0 | Any | Any | SQL thread prints wrong command in the error log |
| 99380 | 2020-04-28 6:28 | 2020-04-29 15:55 | MySQL Server: Replication | Not a Bug (265 days) | S2 | 5.6.16 | Any | Any | Mysql_master-slave replication |
| 99969 | 2020-06-24 8:33 | 2020-06-26 16:08 | MySQL Server: Replication | Not a Bug (207 days) | S3 | 5.7 | Red Hat | Any | replication state is normal, but some transactions are lost |
| 101907 | 2020-12-08 11:39 | 2021-01-11 14:06 | MySQL Server: Replication | Need Feedback (8 days) | S2 | 5.7 | Any | Any | Replication sql_thread hung while executing DML in init state |
| 99006 | 2020-03-20 11:45 | 2020-04-16 10:01 | MySQL Server: Replication | Verified (280 days) | S3 | 5.7 and 8.0 | Any | Any | GTID Synchronisation speed when doing START SLAVE |
| 98799 | 2020-03-02 12:08 | 2021-01-14 8:43 | MySQL Server: Replication | Verified (321 days) | S2 | 5.7, 5.7.29 | Any | Any | Replication failing on valid scenario |
| 101275 | 2020-10-22 13:26 | 2020-10-23 10:23 | MySQL Server: Replication | Verified (88 days) | S3 | 5.7, 5.7.31, 5.7.32, 8.0.22 | Any | Any | rpl_semi_sync_master_enabled=ON without any connected slaves will cause timeout |
| 101351 | 2020-10-28 7:28 | 2020-11-10 12:22 | MySQL Server: Replication | Verified (70 days) | S2 | 5.7, 5.7.32 | Linux | x86 | Replication failure(errno 1399) on dml in XA tr after rollback on timeout |
| 100190 | 2020-07-12 7:13 | 2020-07-13 6:45 | MySQL Server: Replication | Duplicate (190 days) | S3 | 5.7, 8.0 | Any | Any | Allow cleanup of gtid_executed, gtid_purged on a master, live |
| 100189 | 2020-07-12 7:11 | 2020-07-13 5:40 | MySQL Server: Replication | Duplicate (190 days) | S3 | 5.7, 8.0 | Any | Any | Allow cleanup of gtid_executed, gtid_purged on a master, live |
| 98743 | 2020-02-26 1:02 | 2020-02-26 7:04 | MySQL Server: Replication | Verified (328 days) | S1 | 5.7,8.0, 5.7.29, 8.0.19 | Any | Any | Invalid entry on mysql.gtid_executed table is unrecoverable |
| 98840 | 2020-03-05 10:32 | 2020-03-13 2:21 | MySQL Server: Replication | Can't repeat (312 days) | S1 | 5.7.22 | Linux | x86 | sql syntax error on replication slave(using prepared statement) |
| 99440 | 2020-05-05 7:16 | 2020-12-03 13:37 | MySQL Server: Replication | Duplicate (47 days) | S2 | 5.7.26 | Linux | x86 | Threads of MTS Slave randomly stuck |
| 99082 | 2020-03-26 11:26 | 2020-03-27 6:46 | MySQL Server: Replication | Verified (298 days) | S1 | 5.7.27, 5.7.29 | Any | Any | Problem with replication: XA transaction, temp tables and row based binlog |
| 100518 | 2020-08-13 15:08 | 2020-08-30 21:18 | MySQL Server: Replication | Can't repeat (142 days) | S2 | 5.7.29 | CentOS | Any | Auto-increment value in UPDATE conflicts with internally generated values |
| 101795 | 2020-11-30 7:03 | 2020-12-03 2:58 | MySQL Server: Replication | Duplicate (47 days) | S1 | 5.7.29-32 | CentOS (7.8) | x86 | slave io_thread error,Relay log write failure: could not queue event from master |
| 101948 | 2020-12-10 8:00 | 2020-12-31 12:11 | MySQL Server: Replication | Verified (19 days) | S3 | 5.7.29, 5.7.32 | Any | Any | heartbeat is not compatible with local info |
| 99200 | 2020-04-07 18:56 | 2020-04-30 12:13 | MySQL Server: Replication | Verified (264 days) | S2 | 5.7.29, 8.0.19 | Any | Any | CREATE USER get stuck on SHOW PROCESSLIST and ps.threads on slave |
| 101339 | 2020-10-27 12:59 | 2020-10-28 8:18 | MySQL Server: Replication | Verified (83 days) | S3 | 5.7.29，8.018, 8.0.22, 5.7.32 | Linux | x86 | The binlog file was incorrectly purged |
| 101567 | 2020-11-11 19:22 | 2020-11-14 1:45 | MySQL Server: Replication | Verified (67 days) | S2 | 5.7.30/5.7.31 | Any | Any | Generated column as primary key breaks replication |
| 102100 | 2020-12-31 10:58 | 2020-12-31 12:03 | MySQL Server: Replication | Verified (19 days) | S3 | 5.7.31, 8.0.22, 5.7.32 | Any | Any | DCL commands are not replicated witch certain replication filters |
| 101955 | 2020-12-10 13:51 | 2020-12-31 12:11 | MySQL Server: Replication | Verified (40 days) | S3 | 5.7.32 | Any | Any | "heartbeat is not compatible with local info" error message has garbled text |
| 101964 | 2020-12-10 19:57 | 2020-12-11 8:24 | MySQL Server: Replication | Verified (39 days) | S3 | 5.7.32, 8.0.22 | Any | Any | relay_log_space_limit + stopped sql_thread will stop fetching logs silently |
| 100723 | 2020-09-03 7:30 | 2020-09-08 19:33 | MySQL Server: Replication | Verified (134 days) | S5 | 8.0 | Any | Any | slow MTS recovery in startup |
| Showing 1-30 of 55 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
