« 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 |
---|---|---|---|---|---|---|---|---|---|
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 |
91008 | 2018-05-24 11:03 | 2024-02-19 16:17 | MySQL Server: Replication | Not a Bug (2080 days) | S2 | 5.7.21 | CentOS (CentOS (2.6.32-696.23.1.el6.x86_64 )) | x86 | mysql stop for multi-threaded slave gives error code 1756 |
91016 | 2018-05-25 2:56 | 2018-05-28 16:13 | MySQL Server: Replication | Not a Bug (2132 days) | S3 | 5.7.22 | CentOS (7.3) | Any | mysql semi-sync replication issue |
90822 | 2018-05-10 10:31 | 2018-05-14 3:39 | MySQL Server: Replication | Not a Bug (2146 days) | S3 | 5.7.18 | Red Hat (6.8) | x86 | timed auto send “start slave” |
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 |
90107 | 2018-03-16 11:18 | 2018-04-20 11:46 | MySQL Server: Replication | Not a Bug (2170 days) | S3 | 5.7.21-enterprise-commercial-advanced-lo | CentOS (6.9 (Final)) | Any (x86_64) | RSync through snapshot using Multi-Thread replication fails because of duplicate |
43457 | 2009-03-06 14:24 | 2018-04-11 13:22 | MySQL Server: Replication | Not a Bug (2179 days) | S3 | 5.1, 6.0 | Any | Any | replicate-ignore-db behaves differently with different binlog formats |
43992 | 2009-03-31 17:43 | 2018-04-11 13:14 | MySQL Server: Replication | Not a Bug (2179 days) | S3 | 5.0+ | Any | Any | slave sql thread can't tune own sql_mode via @@global.sql_mode |
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 |
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 |
88289 | 2017-10-30 4:01 | 2017-11-17 5:40 | MySQL Server: Replication | Not a Bug (2324 days) | S3 | 5.7.18-log MySQL Community Server (GPL) | CentOS (Linux localhost.localdomain 3.10.0-123.el7.x86_64) | Any | Replication Binlog format change. |
88019 | 2017-10-07 8:03 | 2017-10-09 21:29 | MySQL Server: Replication | Not a Bug (2363 days) | S1 | 5.7.19 | Windows | Any | multi source replication Adding Multiple Databases to replication,binlog |
87102 | 2017-07-18 4:23 | 2017-09-20 6:23 | MySQL Server: Replication | Not a Bug (2382 days) | S2 | 5.6.36 | CentOS (CentOS 6,7. x86_64) | Any | Changing MASTER_DELAY to 0 purges all binlogs and makes recovery impossible |
87212 | 2017-07-26 18:42 | 2017-08-02 4:21 | MySQL Server: Replication | Not a Bug (2431 days) | S5 | 5.7 | Ubuntu | Any | Mysql Server Replication |
82332 | 2016-07-25 8:11 | 2017-07-25 14:13 | MySQL Server: Replication | Not a Bug (2439 days) | S3 | 5.7.13 | CentOS (CentOS release 6.5 (Final)) | Any | replication QUERY(COMMIT or ROLLBACK) or XID_LOG_EVENT is not expected |
86890 | 2017-06-30 14:58 | 2017-07-10 11:57 | MySQL Server: Replication | Not a Bug (2454 days) | S3 | 5.7 | CentOS | Any | Dupllicate Entry in Slave |
85756 | 2017-04-01 10:45 | 2017-04-07 3:55 | MySQL Server: Replication | Not a Bug (2548 days) | S3 | 5.6.20 | CentOS | Any | replication break due to "When @@SESSION.GTID_NEXT is set to a GTID, ....." |
84475 | 2017-01-11 22:48 | 2017-01-23 12:19 | MySQL Server: Replication | Not a Bug (2622 days) | S3 | 5.7.11 | Ubuntu | Any | Frequent slave reconnects and zombies thread warnings when master is idle |
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 |
73257 | 2014-07-10 11:08 | 2016-09-27 13:15 | MySQL Server: Replication | Not a Bug (2740 days) | S1 | 5.6.19 | Linux (CentOS 6.5) | Any | Slave doesn't detect blocking IPTABLES to master server |
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 |
82159 | 2016-07-08 5:51 | 2016-08-09 13:30 | MySQL Server: Replication | Not a Bug (2789 days) | S3 | 5.7.13 | CentOS | Any | mysql.gtid_executed is not updated. after restore. |
80934 | 2016-04-01 14:53 | 2016-05-12 9:34 | MySQL Server: Replication | Not a Bug (2878 days) | S2 | 5.7.11 | Windows (Server 2012 R2) | Any | Replication fails as trigger exists in dumped database. |
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 |
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 |
79272 | 2015-11-13 14:08 | 2016-10-17 14:59 | MySQL Server: Replication | Not a Bug (3059 days) | S2 | Linux | Any | MySQl 5.5 master fails to replicate to MySQL 5.7.9 | |
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 |
76805 | 2015-04-23 11:05 | 2015-04-23 11:30 | MySQL Server: Replication | Not a Bug (3263 days) | S2 | 5.6.24 | Linux (CentOS 6.2) | Any | Unable to configure the Slave host for the Database Replication |
74204 | 2014-10-03 7:38 | 2014-10-03 9:14 | MySQL Server: Replication | Not a Bug (3465 days) | S1 | 5.6.21 | FreeBSD (9.3-amd64) | Any | Missing / duplicated records after master crash |
69324 | 2013-05-27 8:46 | 2014-07-21 19:43 | MySQL Server: Replication | Not a Bug (3539 days) | S3 | 5.5.22 | Linux | Any | mysql issues delete statement in log for memory table when executing query |
« Show Previous 30 Entries | Showing 31-60 of 232 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |