« Show Previous 30 Entries | Showing 31-60 of 131 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
77438 | 2015-06-22 15:46 | 2018-02-12 7:36 | MySQL Server: Replication | Duplicate (2236 days) | S4 | 5.7 | Any | Any | Extend RESET MASTER to allow specifying next binary log. |
86060 | 2017-04-24 21:35 | 2018-02-12 7:41 | MySQL Server: Replication | Verified (2236 days) | S4 | 8.0.1 | Any | Any | Expose counters for monitoring Write Set barriers. |
86079 | 2017-04-25 19:28 | 2018-02-27 17:32 | MySQL Server: Replication | Closed (2221 days) | S2 | 8.0.1 | Any | Any | Deadlock with slave_preserve_commit_order=ON with Bug#86078. |
89141 | 2018-01-08 22:07 | 2018-04-11 16:23 | MySQL Server: Group Replication | Duplicate (2178 days) | S2 | 5.7.20,8.0.3 | Any | Any | Error in Group Replication caused by bad Write Set tracking. |
89194 | 2018-01-11 19:14 | 2018-04-11 16:23 | MySQL Server: Group Replication | Duplicate (2178 days) | S2 | 5.7.20, 8.0.3 | Any | Any | Wrong certification lead to data inconsistency and GR breakage. |
86078 | 2017-04-25 19:14 | 2018-04-12 7:51 | MySQL Server: Replication | Closed (2177 days) | S2 | 8.0.1 | Any | Any | Bad Write Set tracking with UNIQUE KEY on a DELETE followed by an INSERT. |
89146 | 2018-01-08 22:16 | 2018-06-20 16:45 | MySQL Server: Group Replication | Closed (2108 days) | S3 | 5.7.20, 8.0.3 | Any | Any | Binlog name and Pos are wrong in group_replication_applier channel's error msgs |
91455 | 2018-06-28 8:34 | 2018-06-29 4:53 | MySQL Server | Duplicate (2099 days) | S4 | Linux | Any | Implement core dump size reduction. | |
86926 | 2017-07-04 11:24 | 2018-06-29 11:49 | MySQL Server: Partitions | Closed (2099 days) | S2 | 5.7.17-log | Any | Any | The field table_name (varchar(64)) from mysql.innodb_table_stats can overflow. |
89143 | 2018-01-08 22:10 | 2018-07-02 14:06 | MySQL Server: Replication | Closed (2163 days) | S2 | 5.7.20 | Any | Any | Commit order deadlock + retry logic is not considering trx error cases |
91766 | 2018-07-23 14:59 | 2018-07-24 13:24 | MySQL Server: Replication | Verified (2074 days) | S2 | 5.7.22 | Any | Any | Log of replication position when running CHANGE MASTER TO is wrong. |
91737 | 2018-07-20 11:40 | 2018-07-24 13:35 | MySQL Server: Replication | Verified (2074 days) | S4 | 5.7.22 | Any | Any | Please log GTID_EXECUTED when running RESET MASTER. |
91741 | 2018-07-20 14:06 | 2018-07-24 20:32 | MySQL Server: Replication | Verified (2074 days) | S4 | 5.7.22 | Any | Any | Improve Start binlog_dump log on master. |
75395 | 2015-01-02 14:46 | 2018-07-25 17:16 | MySQL Server: Documentation | Closed (2073 days) | S4 | 5.7.5 | Any | Any | Explain relation between slave_preserve_commit_order and binlog_order_commit. |
92012 | 2018-08-14 14:47 | 2018-08-15 21:59 | MySQL Server: Documentation | Closed (2052 days) | S3 | 8.0, 5.7, 5.6 | Any | Any | Wrong default for thread_cache_size in "How MySQL Uses Threads for Client Cnx". |
75393 | 2015-01-02 14:45 | 2018-08-21 17:54 | MySQL Server: Replication | Open (2046 days) | S4 | 5.7.5 | Any | Any | Clarify the way the table mysql.gtid_executed is updated. |
82667 | 2016-08-20 11:19 | 2018-08-31 10:53 | MySQL Server: Documentation | Closed (2049 days) | S3 | 5.6 and 5.7 documentations | Any | Any | Please clarify resiliency introduced by master_info_repository to TABLE. |
92064 | 2018-08-18 18:39 | 2018-08-31 12:09 | MySQL Server: Documentation | Closed (2036 days) | S3 | 5.6, 5.7, 8.0 | Any | Any | Information for the recovery of the IO thread is NOT in mysql.slave_master_info. |
85977 | 2017-04-18 2:02 | 2018-11-02 15:03 | MySQL Server: Documentation | Verified (2536 days) | S3 | 5.7 and 8.0 | Any | Any | The doc. of slave-parallel-type=LOGICAL_CLOCK wrongly reference Group Commit. |
92024 | 2018-08-15 17:48 | 2018-11-02 17:53 | MySQL Server: Connection Handling | Closed (1973 days) | S3 | 5.7.23, 8.0.12, 5.6.41 | Any | Any | Setting thread_cache_size to 0 does not empty the Thread Cache. |
93843 | 2019-01-07 17:21 | 2019-01-14 9:24 | MySQL Server: Replication | Duplicate (1904 days) | S2 | 5.7.24 | Any | Any | Setting MASTER_DELAY to 0 on a stopped delayed slave wipes the relay-log. |
75394 | 2015-01-02 14:45 | 2019-01-24 10:53 | MySQL Server: Documentation | Closed (1890 days) | S4 | 5.6 and 5.7 | Any | Any | Improve documentation of binlog_order_commits. |
89142 | 2018-01-08 22:09 | 2019-04-30 15:41 | MySQL Server: Group Replication | Closed (1794 days) | S4 | 5.7.20, 8.0.3 | Any | Any | Make FLUSH RELAY LOGS work for Group Replication. |
95478 | 2019-05-22 15:31 | 2019-05-23 13:36 | MySQL Server: InnoDB storage engine | Verified (1771 days) | S4 | 5.7.26 | Any | Any | CREATE TABLE LIKE does not honour ROW_FORMAT. |
95486 | 2019-05-23 9:54 | 2019-05-23 13:38 | MySQL Server: Partitions | Verified (1771 days) | S4 | 5.7.26 | Any | Any | Allow to ALTER the ROW_FORMAT of a partition. |
89148 | 2018-01-08 22:23 | 2019-06-04 1:24 | MySQL Server: Group Replication | Verified (2236 days) | S4 | 5.7.20 and 8.0.3 | Any | Any | The timestamp of the GITD events in the GR relay log look wrong. |
84467 | 2017-01-11 8:22 | 2019-06-28 19:53 | MySQL Server: InnoDB storage engine | Verified (2073 days) | S3 | 5.7.17-log | Any | Any | ALTERing KEY_BLOCK_SIZE keeps the old kbs in KEYs. |
96134 | 2019-07-09 5:43 | 2019-07-09 13:36 | MySQL Server: Replication | Verified (1724 days) | S4 | 5.6, 5.7, 8.0 | Any | Any | Please provide control functions for the IO Thread. |
89195 | 2018-01-11 19:15 | 2019-07-25 14:45 | MySQL Server: Group Replication | Closed (1708 days) | S2 | 5.7.20, 8.0.3 | Any | Any | Total ordering of transactions is not respected in Group Replication. |
93395 | 2018-11-29 6:50 | 2019-07-30 7:34 | MySQL Server: Replication | Duplicate (1703 days) | S2 | 5.7.24 | Any | Any | ALTER USER succeeds on master but fails on slave. |
« Show Previous 30 Entries | Showing 31-60 of 131 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |