| Showing 1-30 of 435 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 91766 | 2018-07-23 14:59 | 2018-07-24 13:24 | MySQL Server: Replication | Verified (2101 days) | S2 | 5.7.22 | Any | Any | Log of replication position when running CHANGE MASTER TO is wrong. |
| 91812 | 2018-07-27 2:52 | 2021-03-22 18:14 | MySQL Server: Replication | Verified (1129 days) | S2 | 5.7.22 | Any | Any | Slave replay stops because of explicit_defaults_for_timestamp between B and C |
| 91829 | 2018-07-30 9:51 | 2018-07-30 12:55 | MySQL Server: Replication | Verified (2095 days) | S2 | 5.7.22, 5.7.23, 8.0.12 | Any | Any | Class Gtid_state has a wrong function to_string(char *buf) |
| 92109 | 2018-08-21 17:53 | 2021-06-15 7:48 | MySQL Server: Replication | Verified (1083 days) | S2 | 5.7, 8.0 | Any | Any | Please make replication crash safe with GITD and less durable setting (bis). |
| 92126 | 2018-08-22 14:21 | 2018-08-22 14:28 | MySQL Server: Replication | Verified (2072 days) | S3 | Any | Any | Contribution: Add enable cleartext plugin option to binlog reader | |
| 92252 | 2018-08-31 1:14 | 2019-05-03 12:08 | MySQL Server: Replication | Verified (2060 days) | S2 | 5.7.23 | Any | Any | Mysql generates gtid gaps because of option slave-skip-errors |
| 93081 | 2018-11-05 11:08 | 2020-03-19 13:04 | MySQL Server: Replication | Verified (1994 days) | S2 | 5.6, 5.7, 8.0 | Any | Any | Please implement a better relay log recovery. |
| 93761 | 2018-12-29 2:45 | 2019-03-20 7:38 | MySQL Server: Replication | Verified (1873 days) | S2 | 5.7.22 | Red Hat (6.5) | Any | optimize table cause the slave MTS deadlock! |
| 93779 | 2019-01-02 9:18 | 2019-01-30 14:53 | MySQL Server: Replication | Verified (1911 days) | S1 | 5.7.24 | Windows | Any | dml in table with trigger to other Table map in binlog lead to slave sql stopped |
| 93786 | 2019-01-02 16:42 | 2019-01-03 6:35 | MySQL Server: Replication | Verified (1938 days) | S3 | 5.7.24, 8.0.13 | Any | Any | SHOW BINLOG EVENTS FROM <bad offset> is not diagnosed for 1-3 and invalid offset |
| 93948 | 2019-01-16 8:23 | 2019-02-08 4:52 | MySQL Server: Replication | Verified (1902 days) | S3 | 8.0.13 | Any | Any | XID inconsistency on master-slave with CTAS |
| 93957 | 2019-01-17 8:25 | 2023-07-13 3:11 | MySQL Server: Replication | Verified (1667 days) | S2 | 5.7.24 | Any | Any | slave_compressed_protocol doesn't work with semi-sync replication in MySQL-5.7 |
| 94013 | 2019-01-23 9:08 | 2019-02-01 0:32 | MySQL Server: Replication | Verified (1910 days) | S3 | 5.7.24 | CentOS | Any | Add PAD_CHAR_TO_FULL_LENGTH will cause master/slave replication status is error |
| 94302 | 2019-02-13 5:19 | 2019-02-13 11:21 | MySQL Server: Replication | Verified (1897 days) | S3 | 5.7.18, 5.7.25 | Any | Any | reset master could not break dump thread in some cases |
| 94452 | 2019-02-23 9:20 | 2020-03-19 13:05 | MySQL Server: Replication | Verified (1885 days) | S3 | 5.6.42, 5.6.43 | Any | Any | "Slave: Out of memory" on ALTER TABLE when not able to write to tmpdir . |
| 94803 | 2019-03-28 2:47 | 2020-03-09 13:03 | MySQL Server: Replication | Verified (1511 days) | S3 | 5.7.24 | Any | Any | rpl sql_thread may broken due to XAER_RMFAIL error for unfinished xa transaction |
| 94827 | 2019-03-29 7:47 | 2020-10-07 12:04 | MySQL Server: Replication | Verified (1853 days) | S3 | 5.7.25 | CentOS (7) | x86 | Error 1032 could be more informative (handler error HA_ERR_KEY_NOT_FOUND) |
| 95008 | 2019-04-12 13:00 | 2019-04-17 15:05 | MySQL Server: Replication | Verified (1834 days) | S3 | 5.6.43 - 8.0.15 | Linux (CentOS 7) | x86 | applying binary log doesn't work with blackhole engine tables |
| 95064 | 2019-04-19 11:05 | 2021-04-27 20:23 | MySQL Server: Replication | Verified (1832 days) | S2 | 5.7.22 | Any | x86 | slave server may has gaps in Executed_Gtid_Set when a special case happen |
| 95235 | 2019-05-03 5:41 | 2019-05-10 1:08 | MySQL Server: Replication | Verified (1818 days) | S2 | 8.0.16 | Fedora (fc30) | x86 | ABRT:Can't generate a unique log-filename binlog.(1-999), while rotating the bin |
| 95249 | 2019-05-05 8:11 | 2023-05-04 16:25 | MySQL Server: Replication | Verified (1815 days) | S2 | mysql-5.7 | Any | Any | stop slave permanently blocked |
| 95269 | 2019-05-07 2:22 | 2019-08-05 8:10 | MySQL Server: Replication | Verified (1814 days) | S3 | 8.0.16 | Any | Any | binlog_row_image=minimal causes assertion failure |
| 95294 | 2019-05-08 11:39 | 2019-05-10 12:09 | MySQL Server: Replication | Verified (1813 days) | S3 | 5.6, 5.7, 8.0, 5.6.44, 5.7.26 | Any | Any | non-existent log_bin dir cause mysqld SIGSEGV crash at startup |
| 95319 | 2019-05-09 13:54 | 2019-05-21 7:17 | MySQL Server: Replication | Verified (1800 days) | S3 | 5.6,5.7, 5.7.26 | Any | Any | SHOW SLAVE HOST coalesces certain server_id's into one |
| 95547 | 2019-05-27 14:37 | 2019-05-31 11:57 | MySQL Server: Replication | Verified (1790 days) | S2 | 5.7.26 | Any | Any | MySQL restarts automatically after ABORT_SERVER due to disk full |
| 95600 | 2019-06-02 14:59 | 2019-06-21 9:02 | MySQL Server: Replication | Verified (1770 days) | S3 | Any | Any | Pervious-gtid lost gtid in binlog file | |
| 95738 | 2019-06-11 15:15 | 2019-06-11 15:47 | MySQL Server: Replication | Verified (1779 days) | S3 | Any | Any | Contribution: Control the Maximum speed(KB/s) to read binlog from master | |
| 95739 | 2019-06-11 15:15 | 2019-06-11 15:52 | MySQL Server: Replication | Verified (1779 days) | S3 | Any | Any | Contribution: Compressed binary log | |
| 95829 | 2019-06-17 6:04 | 2019-10-11 6:08 | MySQL Server: Replication | Verified (1657 days) | S3 | 8.0.13 | Any | Any | mysql DB statements failing on slave even after using replicate-ignore-db=mysql |
| 95863 | 2019-06-18 14:59 | 2022-11-03 17:50 | MySQL Server: Replication | Verified (1371 days) | S3 | 5.7.26,8.0.16, 5.7.27 | Any | Any | MTS ordered commit may cause deadlock |
| Showing 1-30 of 435 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
