| Showing 1-30 of 51 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 69493 | 2013-06-17 17:53 | 2018-09-25 21:51 | Tests: Replication | Duplicate (3641 days) | S7 | 5.6.12 | Any | Any | Slave deadlock by show slave status, global read lock and slave_master_info |
| 70327 | 2013-09-13 8:05 | 2014-09-30 13:47 | MySQL Server: Replication | Closed (3199 days) | S2 | 5.6.13 | Any | Any | Assersion error when setting future binlog file/pos with semisync |
| 68506 | 2013-02-27 7:23 | 2015-05-08 15:06 | MySQL Server: Replication | Closed (3674 days) | S2 | 5.6.10 | Any | Any | Got SIGSEGV on MTS recovery + SQL thread error |
| 69096 | 2013-04-29 20:52 | 2013-07-09 10:01 | MySQL Server: Replication | Closed (3620 days) | S2 | 5.6.11 | Any | Any | GTID_NEXT_LIST session variable is not visible |
| 69097 | 2013-04-29 22:51 | 2022-05-05 9:01 | MySQL Server: Replication | Closed (3176 days) | S2 | 5.6.11 | Any | Any | mysqld scans all binary logs on crash recovery |
| 54605 | 2010-06-18 6:22 | 2011-02-16 23:44 | MySQL Server: Replication | Won't fix (4600 days) | S3 | 5.0, 5.1, 5.5 | Any | Any | Xid_log_event::do_apply_event() should update future_group_master_log_pos |
| 69943 | 2013-08-07 0:46 | 2014-02-03 10:12 | MySQL Server: Replication | Closed (3507 days) | S1 | 5.6.13 | Any | Any | Transactions skipped on slave after "stop/start slave" using GTID replication |
| 70218 | 2013-09-02 21:42 | 2014-03-28 19:21 | MySQL Server: Replication | Closed (3418 days) | S5 | 5.6.13 | Any | Any | Semisync master plugin with many slaves causes plugin_lock mutex contentions |
| 70307 | 2013-09-12 0:33 | 2015-02-12 12:37 | MySQL Server: Replication | Closed (3100 days) | S2 | 5.6.13 | Any | Any | Another deadlock on FLUSH TABLES WITH READ LOCK + SHOW SLAVE STATUS |
| 69341 | 2013-05-29 0:55 | 2016-04-07 5:46 | MySQL Server: Replication | Closed (3624 days) | S5 | 5.6.11 | Any | Any | semi-sync replication is very slow with many clients |
| 70342 | 2013-09-13 22:18 | 2013-09-21 15:44 | MySQL Server: Replication | Verified (3546 days) | S5 | 5.6.13 | Any | Any | master_info_repository=FILE calls my_b_printf too often |
| 70659 | 2013-10-18 18:31 | 2021-05-07 12:42 | MySQL Server: Replication | Verified (3516 days) | S3 | 5.6.14 | Any | Any | Make crash safe slave work with gtid + less durable settings |
| 70669 | 2013-10-20 4:25 | 2014-03-29 8:25 | MySQL Server: Replication | Closed (3387 days) | S2 | 5.6.14 | Any | Any | Slave can't continue replication after master's crash recovery |
| 70711 | 2013-10-23 18:21 | 2015-06-24 4:30 | MySQL Server: Replication | Closed (2968 days) | S3 | 5.6.14 | Any | Any | mysqlbinlog prints invalid SQL from relay logs when GTID is enabled |
| 71130 | 2013-12-11 20:43 | 2013-12-17 17:35 | MySQL Server: Replication | Verified (3459 days) | S5 | 5.6.15 | Any | Any | 5.6 SQL thread is much slower than 5.1/5.5 |
| 89272 | 2018-01-16 22:52 | 2018-06-19 10:29 | MySQL Server: Replication | Closed (1847 days) | S2 | 5.6.39 | Any | Any | Binlog and Engine become inconsistent when binlog cache file gets out of space |
| 105924 | 2021-12-16 20:40 | 2022-07-25 15:16 | MySQL Server: Replication | Closed (317 days) | S5 | 8.0.22, 8.0.27 | Any | Any | SHOW SLAVE STATUS became expensive for Replica->Slave column name conversions |
| 68220 | 2013-01-29 18:59 | 2020-03-09 18:32 | MySQL Server: Replication | Verified (3780 days) | S3 | 5.6.9, 5.7.1 | Any | Any | innodb_rows_updated is misleading on slave when *info_repository = TABLE |
| 68351 | 2013-02-12 18:44 | 2013-02-13 8:11 | MySQL Server: Replication | Verified (3766 days) | S3 | 5.6.10 | Any | Any | Out of range updates/deletes are not written to binlog |
| 67879 | 2012-12-11 22:59 | 2014-12-19 4:59 | MySQL Server: Replication | Closed (3759 days) | S2 | 5.1, 5.5, 5.6 | Any | Any | Slave deadlock caused by stop slave, show slave status and global read lock |
| 62055 | 2011-08-02 10:24 | 2011-12-19 1:29 | MySQL Server: Replication | Closed (4188 days) | S3 | 5.1.59, 5.5.15 | Any | Any | Race condition in check_temp_dir() from multiple mysqld instances |
| 68229 | 2013-01-31 1:34 | 2013-01-31 14:03 | MySQL Server: Replication | Closed (3779 days) | S2 | 5.6.9 | Any | Any | MTS may get SIGSEGV because of partial deletes on rli->curr_group_da |
| 68250 | 2013-02-02 0:35 | 2013-04-23 13:10 | MySQL Server: Replication | Not a Bug (3697 days) | S3 | 5.6.9 | Any | Any | Current semi-synchronous replication may cause deadlock |
| 68251 | 2013-02-02 1:09 | 2013-05-28 6:58 | MySQL Server: Replication | Closed (3662 days) | S3 | 5.6.9 | Any | Any | 3-way deadlock on semisync replication and binlog rotate |
| 60964 | 2011-04-24 7:51 | 2013-01-21 14:42 | MySQL Server: Row Based Replication ( RBR ) | Not a Bug (3789 days) | S3 | 5.1.56, 5.6.3 | Any | Any | row based relay log events are lost from mysqlbinlog output |
| 61384 | 2011-06-02 11:55 | 2011-06-02 12:01 | MySQL Server: Security: Privileges | Duplicate (4388 days) | S3 | 5.1.57 | Any | Any | Can't connect MySQL 5.1.57 from old(4.0) clients |
| 66567 | 2012-08-28 7:57 | 2012-11-13 18:32 | MySQL Server: Security: Privileges | Closed (3858 days) | S5 | 5.6.6, 5.6.7 | Any | Any | my_rnd_ssl() is very expensive for authentication |
| 70577 | 2013-10-09 21:47 | 2013-10-15 18:19 | MySQL Server: Performance Schema | Closed (3522 days) | S3 | 5.6.14 | Any | Any | Read/Write mutexes on Binlog delegate classes are not counted on perf schema |
| 70641 | 2013-10-16 23:56 | 2014-09-25 11:46 | MySQL Server: Partitions | Closed (3235 days) | S3 | 5.6.14 | Any | Any | 5.6 partitions use much more memory than 5.1 |
| 70265 | 2013-09-06 18:10 | 2015-08-23 20:45 | MySQL Server: Partitions | Verified (3558 days) | S5 | 5.6.13 | Any | Any | Optimizer under-estimates rows when there are many unmatched partitions |
| Showing 1-30 of 51 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
