« Show Previous 30 Entries | Showing 31-60 of 232 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
60955 | 2011-04-22 19:35 | 2011-06-14 10:26 | MySQL Server: Replication | Not a Bug (4672 days) | S3 | 5.1.56 | Any | Any | Error executing trigger on slave results in replication event replay |
61268 | 2011-05-23 19:06 | 2013-01-16 17:08 | MySQL Server: Replication | Not a Bug (4090 days) | S5 | 5.5.12 | Any | Any | replication is not transaction-aware, which results in extremely excessive fsync |
68070 | 2013-01-11 3:01 | 2014-02-03 10:41 | MySQL Server: Replication | Not a Bug (3721 days) | S2 | 5.6.9 | Any | Any | Maybe there existed memory leak in code |
68250 | 2013-02-02 0:35 | 2013-04-23 13:10 | MySQL Server: Replication | Not a Bug (3993 days) | S3 | 5.6.9 | Any | Any | Current semi-synchronous replication may cause deadlock |
69095 | 2013-04-29 19:01 | 2013-07-08 12:09 | MySQL Server: Replication | Not a Bug (3917 days) | S1 | 5.5 | Any | Any | binlog_format=STATEMENT makes execution of BINLOG stmts or ROW events to fail |
70237 | 2013-09-04 5:43 | 2018-12-10 13:23 | MySQL Server: Replication | Not a Bug (1936 days) | S3 | 5.5,5.6 | Any | Any | the mysqladmin shutdown hangs |
70877 | 2013-11-11 7:44 | 2013-11-19 7:53 | MySQL Server: Replication | Not a Bug (3783 days) | S3 | MySQL 5.x, 5.5.34 | Any | Any | DCL statement is failing on slave with replicate-ignore-db=mysql |
71083 | 2013-12-05 3:59 | 2013-12-11 2:18 | MySQL Server: Replication | Not a Bug (3761 days) | S2 | 5.6.15 | Any | Any | updating mysql.slave_relay_log_info depends on sync_relay_log_info |
72035 | 2014-03-13 20:19 | 2014-03-17 19:01 | MySQL Server: Replication | Not a Bug (3665 days) | S3 | MySQL 5.5.35 -and- 5.5.24 | Any | Any | MASTER_LOG_POS changes |
75310 | 2014-12-25 10:59 | 2018-04-25 15:14 | MySQL Server: Replication | Not a Bug (2165 days) | S3 | 5.6.22 | Any | Any | Error message for SSL validation failure is not shown for replication |
76249 | 2015-03-10 21:42 | 2018-03-09 9:47 | MySQL Server: Replication | Not a Bug (2212 days) | S3 | 5.6 | Any | Any | Replication should ignore safe update mode |
77020 | 2015-05-13 9:55 | 2019-04-11 19:40 | MySQL Server: Replication | Not a Bug (1814 days) | S3 | >= 5.5 | Any | Any | MASTER_CONNECT_RETRY should be a global variable |
77187 | 2015-05-29 6:37 | 2015-06-29 14:53 | MySQL Server: Replication | Not a Bug (3196 days) | S3 | 5.7.7rc, 5.7.8 | Any | Any | START SLAVE no error if sql thread running + GLOBAL SQL_SLAVE_SKIP_COUNTER > 1 |
80160 | 2016-01-26 18:21 | 2016-11-28 6:48 | MySQL Server: Replication | Not a Bug (2678 days) | S3 | 5.6.27 | Any | Any | slave_master_info is locked with SERIALIZABLE |
80342 | 2016-02-11 15:04 | 2016-02-11 15:42 | MySQL Server: Replication | Not a Bug (2969 days) | S3 | 5.7.11 | Any | Any | session_track_gtids is not optimal |
80394 | 2016-02-16 12:37 | 2016-03-07 9:33 | MySQL Server: Replication | Not a Bug (2944 days) | S2 | 5.7.11 | Any | Any | incorrect semi-sync replication status handling |
83007 | 2016-09-15 8:33 | 2016-09-15 13:28 | MySQL Server: Replication | Not a Bug (2752 days) | S3 | 8.0.0 | Any | Any | GRANT statement breaks 5.7→8.0 replication w/ GTID |
89065 | 2017-12-27 14:13 | 2018-01-08 12:58 | MySQL Server: Replication | Not a Bug (2272 days) | S2 | 5.6.35 | Any | Any | sync_binlog=1 on a busy server and slow binary log filesystem stalls slaves |
89959 | 2018-03-08 10:59 | 2019-04-12 9:08 | MySQL Server: Replication | Not a Bug (1957 days) | S2 | 8.0.4 | Any | Any | Replication fails when users are created using caching_sha2_password |
91903 | 2018-08-06 3:34 | 2018-08-06 6:19 | MySQL Server: Replication | Not a Bug (2062 days) | S2 | 5.7.21 | Any | Any | replication filter should base on channel scopeinstead of global scope |
93393 | 2018-11-29 3:59 | 2018-11-29 9:49 | MySQL Server: Replication | Not a Bug (1947 days) | S1 | 5.7.23 | Any | Any | Some commit may not written to binlog |
93978 | 2019-01-18 9:44 | 2019-01-22 14:04 | MySQL Server: Replication | Not a Bug (1893 days) | S3 | 5.7.23 | Any | Any | XA COMMIT success with same xid |
95439 | 2019-05-21 1:41 | 2019-05-21 17:56 | MySQL Server: Replication | Not a Bug (1774 days) | S3 | 5.7.26 | Any | Any | FLUSH LOGS is not added to binlog |
96026 | 2019-06-28 12:40 | 2019-07-01 13:21 | MySQL Server: Replication | Not a Bug (1733 days) | S3 | Any | Any | The HA instance causes FEDERATED engine operations to be performed multiple time | |
96089 | 2019-07-04 7:01 | 2019-08-12 5:12 | MySQL Server: Replication | Not a Bug (1691 days) | S2 | 5.5.62 | Any | Any | row based replication ignores replicate_wild_ignore_table setting |
97808 | 2019-11-27 6:20 | 2019-12-27 9:12 | MySQL Server: Replication | Not a Bug (1554 days) | S2 | 5.6 | Any | Any | Truncate table in Master-slave replication |
98069 | 2019-12-25 10:12 | 2020-01-09 4:53 | MySQL Server: Replication | Not a Bug (1550 days) | S3 | 5.7 | Any | Any | No error on slave while trigger for binlog_format="statement" and read_only is 1 |
99380 | 2020-04-28 6:28 | 2020-04-29 15:55 | MySQL Server: Replication | Not a Bug (1430 days) | S2 | 5.6.16 | Any | Any | Mysql_master-slave replication |
106206 | 2022-01-19 6:57 | 2022-01-20 16:24 | MySQL Server: Replication | Not a Bug (799 days) | S2 | 8.0.25 | Any | Any | replicate-wild-do-table causes unknown database My-001049 for CREATE PROCEDURE |
106942 | 2022-04-07 10:44 | 2022-04-19 9:40 | MySQL Server: Replication | Not a Bug (710 days) | S3 | 8.0.28 | Any | Any | alter user may lead replication broken with error 1396 |
« Show Previous 30 Entries | Showing 31-60 of 232 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |