| Showing 1-30 of 48 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 100076 | 2020-07-02 8:03 | 2020-07-03 7:02 | MySQL Server: Replication | Verified (89 days) | S3 | 5.6, 5.7, 5.7.30, 8.0.20 | Any | Any | Missing db name when alter current db -break slave |
| 98743 | 2020-02-26 1:02 | 2020-02-26 7:04 | MySQL Server: Replication | Verified (217 days) | S1 | 5.7,8.0, 5.7.29, 8.0.19 | Any | Any | Invalid entry on mysql.gtid_executed table is unrecoverable |
| 97207 | 2019-10-14 1:18 | 2019-10-14 10:21 | MySQL Server: Replication | Verified (352 days) | S3 | 5.7.26, 5.7.27 | Any | Any | MySQL Group Replication Old incarnation |
| 99006 | 2020-03-20 11:45 | 2020-04-16 10:01 | MySQL Server: Replication | Verified (169 days) | S3 | 5.7 and 8.0 | Any | Any | GTID Synchronisation speed when doing START SLAVE |
| 99082 | 2020-03-26 11:26 | 2020-03-27 6:46 | MySQL Server: Replication | Verified (187 days) | S1 | 5.7.27, 5.7.29 | Any | Any | Problem with replication: XA transaction, temp tables and row based binlog |
| 99200 | 2020-04-07 18:56 | 2020-04-30 12:13 | MySQL Server: Replication | Verified (153 days) | S2 | 5.7.29, 8.0.19 | Any | Any | CREATE USER get stuck on SHOW PROCESSLIST and ps.threads on slave |
| 99380 | 2020-04-28 6:28 | 2020-04-29 15:55 | MySQL Server: Replication | Not a Bug (154 days) | S2 | 5.6.16 | Any | Any | Mysql_master-slave replication |
| 99497 | 2020-05-09 12:35 | 2020-05-11 5:34 | MySQL Server: Replication | Not a Bug (142 days) | S3 | Ubuntu | Any | Replication with SSL keep return error code 2026 | |
| 99628 | 2020-05-19 9:16 | 2020-05-28 14:59 | MySQL Server: Replication | Verified (132 days) | S2 | 8.0.* | Any | Any | semi sync master not handle ack packet correctly when recv packet timeout |
| 99760 | 2020-06-02 12:33 | 2020-06-26 8:51 | MySQL Server: Replication | Verified (119 days) | S3 | 8.0.16 | Any | Any | Statements involving temporary tables getting logged |
| 99806 | 2020-06-08 16:30 | 2020-07-02 2:41 | MySQL Server: Replication | Verified (114 days) | S3 | Any | Any | replace master/slave terminology with primary/replica | |
| 99969 | 2020-06-24 8:33 | 2020-06-26 16:08 | MySQL Server: Replication | Not a Bug (96 days) | S3 | 5.7 | Red Hat | Any | replication state is normal, but some transactions are lost |
| 98799 | 2020-03-02 12:08 | 2020-03-04 8:24 | MySQL Server: Replication | Verified (210 days) | S2 | 5.7, 5.7.29 | Any | Any | Replication failing on valid scenario |
| 100093 | 2020-07-02 13:21 | 2020-07-07 4:30 | MySQL Server: Replication | Unsupported (85 days) | S3 | 8.0.16, 8.0.18 | Any | Any | Replica error when update mysql.user |
| 100189 | 2020-07-12 7:11 | 2020-07-13 5:40 | MySQL Server: Replication | Duplicate (79 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 | 2020-07-13 6:45 | MySQL Server: Replication | Duplicate (79 days) | S3 | 5.7, 8.0 | Any | Any | Allow cleanup of gtid_executed, gtid_purged on a master, live |
| 100378 | 2020-07-30 8:57 | 2020-08-03 11:58 | MySQL Server: Replication | Can't repeat (58 days) | S3 | 8.0.21 | Any | Any | GROUP_REPLICATION member cannot join |
| 100518 | 2020-08-13 15:08 | 2020-08-30 21:18 | MySQL Server: Replication | Can't repeat (31 days) | S2 | 5.7.29 | CentOS | Any | Auto-increment value in UPDATE conflicts with internally generated values |
| 100591 | 2020-08-20 17:57 | 2020-08-20 19:45 | MySQL Server: Replication | Verified (41 days) | S3 | Any | Any | Contribution: Bug #100586 Assertion failure `m_status == DA_ERROR` in `Diag ... | |
| 100612 | 2020-08-23 11:28 | 2020-08-24 4:49 | MySQL Server: Replication | Verified (37 days) | S3 | 5.6,5.7,8.0 | Any | Any | SQL thread prints wrong command in the error log |
| 100643 | 2020-08-26 11:43 | 2020-08-28 6:11 | MySQL Server: Replication | Verified (33 days) | S3 | 8.0.21 | Ubuntu | Any | Can't connect to MySQL with sync plugin enabled after user creation |
| 100723 | 2020-09-03 7:30 | 2020-09-08 19:33 | MySQL Server: Replication | Verified (23 days) | S5 | 8.0 | Any | Any | slow MTS recovery in startup |
| 100793 | 2020-09-10 7:46 | 2020-09-10 8:05 | MySQL Server: Replication | Verified (20 days) | S2 | 8.0.20, 8.0.21 | CentOS | Any | 'GRANT SELECT, GRANT OPTION ON *.* ' would not write the privileges to binlog |
| 98069 | 2019-12-25 10:12 | 2020-01-09 4:53 | MySQL Server: Replication | Not a Bug (274 days) | S3 | 5.7 | Any | Any | No error on slave while trigger for binlog_format="statement" and read_only is 1 |
| 97345 | 2019-10-23 16:27 | 2020-03-19 13:05 | MySQL Server: Replication | Verified (341 days) | S2 | 5.7.28 | Any | Any | IO Thread not detecting failed master with relay_log_space_limit. |
| 97372 | 2019-10-25 2:13 | 2019-11-26 11:25 | MySQL Server: Replication | Verified (341 days) | S3 | 5.7,5.7.28,8.0.12 | Any | Any | Constructor Query_event must check enough space |
| 97531 | 2019-11-07 11:22 | 2020-02-29 17:35 | MySQL Server: Replication | Closed (267 days) | S1 | 5.7.28, 8.0.18 | Any | Any | 5.7 replication breakage with syntax error with GRANT management |
| 97560 | 2019-11-08 12:32 | 2020-09-28 7:47 | MySQL Server: Replication | Verified | S3 | 5.7.29 | Any | Any | idle & caught up slave has old query shown in "Info" section of processlist... |
| 97694 | 2019-11-19 15:53 | 2019-11-21 5:58 | MySQL Server: Replication | Verified (314 days) | S3 | 8.0.18 | Any | Any | MySQL 8.0.18 fails on STOP SLAVE/START SLAVE stress test |
| 97780 | 2019-11-26 6:05 | 2020-04-14 14:27 | MySQL Server: Replication | Verified (307 days) | S3 | MySQL5.7, 5.7.28 | Any | Any | Two different type engines in Mysql cause error (assert in debug) in Binlog Xa |
| Showing 1-30 of 48 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
