Showing 1-30 of 232 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
113219 | 2023-11-25 13:05 | 2023-12-06 8:02 | MySQL Server: Replication | Not a Bug (113 days) | S3 | MySQL8.0.34,MySQL8.2.0 | Linux | Any | Wrong value of auto_increment while executing load data replace |
112727 | 2023-10-15 4:17 | 2023-10-19 14:46 | MySQL Server: Replication | Not a Bug (161 days) | S3 | MySQL8.0.22, 8.0.23 | Any | Any | MySQL may couldn't solve the error when flush thread caches to binary logs |
111074 | 2023-05-18 12:15 | 2023-05-22 14:07 | MySQL Server: Replication | Not a Bug (311 days) | S2 | 8.0.33 | Red Hat (redhat 8.7) | x86 | start replica encounter Slave_SQL_Running NO with MY-013117 (null) |
110774 | 2023-04-23 13:52 | 2023-04-25 2:49 | MySQL Server: Replication | Not a Bug (338 days) | S3 | 8.0.33 | Any | Any | 'show replica status' set the field_flag of 'Second_Behind_Source' NOTNULL |
108834 | 2022-10-20 11:05 | 2022-11-04 14:14 | MySQL Server: Replication | Not a Bug (510 days) | S3 | all version | Any | Any | MySQL Online DDL add AUTO_INCREMENT |
108104 | 2022-08-10 3:06 | 2022-08-10 12:39 | MySQL Server: Replication | Not a Bug (596 days) | S5 | MySQL5.7.26 | Any | Any | LOCK_status affect transaction performance when do a "show status" command |
106942 | 2022-04-07 10:44 | 2022-04-19 9:40 | MySQL Server: Replication | Not a Bug (709 days) | S3 | 8.0.28 | Any | Any | alter user may lead replication broken with error 1396 |
106206 | 2022-01-19 6:57 | 2022-01-20 16:24 | MySQL Server: Replication | Not a Bug (798 days) | S2 | 8.0.25 | Any | Any | replicate-wild-do-table causes unknown database My-001049 for CREATE PROCEDURE |
104480 | 2021-07-30 20:34 | 2021-08-10 0:34 | MySQL Server: Replication | Not a Bug (961 days) | S2 | 8.0.25 | Debian | x86 | Filtered replication fails on CREATE TABLE statements performed with backticks |
99969 | 2020-06-24 8:33 | 2020-06-26 16:08 | MySQL Server: Replication | Not a Bug (1371 days) | S3 | 5.7 | Red Hat | Any | replication state is normal, but some transactions are lost |
99497 | 2020-05-09 12:35 | 2020-05-11 5:34 | MySQL Server: Replication | Not a Bug (1417 days) | S3 | Ubuntu | Any | Replication with SSL keep return error code 2026 | |
99380 | 2020-04-28 6:28 | 2020-04-29 15:55 | MySQL Server: Replication | Not a Bug (1429 days) | S2 | 5.6.16 | Any | Any | Mysql_master-slave replication |
98069 | 2019-12-25 10:12 | 2020-01-09 4:53 | MySQL Server: Replication | Not a Bug (1549 days) | S3 | 5.7 | Any | Any | No error on slave while trigger for binlog_format="statement" and read_only is 1 |
97808 | 2019-11-27 6:20 | 2019-12-27 9:12 | MySQL Server: Replication | Not a Bug (1553 days) | S2 | 5.6 | Any | Any | Truncate table in Master-slave replication |
96089 | 2019-07-04 7:01 | 2019-08-12 5:12 | MySQL Server: Replication | Not a Bug (1690 days) | S2 | 5.5.62 | Any | Any | row based replication ignores replicate_wild_ignore_table setting |
95077 | 2019-04-22 19:03 | 2019-07-25 23:31 | MySQL Server: Replication | Not a Bug (1708 days) | S3 | 5.7.17-13 | Ubuntu (Ubuntu 16.04) | Any | gtid_owned session variable is always empty, in all circumstances |
96026 | 2019-06-28 12:40 | 2019-07-01 13:21 | MySQL Server: Replication | Not a Bug (1732 days) | S3 | Any | Any | The HA instance causes FEDERATED engine operations to be performed multiple time | |
95439 | 2019-05-21 1:41 | 2019-05-21 17:56 | MySQL Server: Replication | Not a Bug (1773 days) | S3 | 5.7.26 | Any | Any | FLUSH LOGS is not added to binlog |
77020 | 2015-05-13 9:55 | 2019-04-11 19:40 | MySQL Server: Replication | Not a Bug (1813 days) | S3 | >= 5.5 | Any | Any | MASTER_CONNECT_RETRY should be a global variable |
94727 | 2019-03-20 20:23 | 2019-03-28 9:46 | MySQL Server: Replication | Not a Bug (1827 days) | S2 | 8.0.15 | CentOS (7.6.1810/x86_64) | x86 | Replicate_Wild_Ignore_Table is not working for cross database query |
94629 | 2019-03-12 3:20 | 2019-03-14 11:06 | MySQL Server: Replication | Not a Bug (1841 days) | S1 | 5.7.21 | CentOS (CentOS Linux release 7.6.1810 (Core)) | Any | no variable can skip a single channel error in mysql replication |
85688 | 2017-03-29 16:16 | 2019-02-21 0:40 | MySQL Server: Replication | Not a Bug (1862 days) | S1 | 5.7 | CentOS | Any | Replication with SSL return error 2026 |
93978 | 2019-01-18 9:44 | 2019-01-22 14:04 | MySQL Server: Replication | Not a Bug (1892 days) | S3 | 5.7.23 | Any | Any | XA COMMIT success with same xid |
70237 | 2013-09-04 5:43 | 2018-12-10 13:23 | MySQL Server: Replication | Not a Bug (1935 days) | S3 | 5.5,5.6 | Any | Any | the mysqladmin shutdown hangs |
93393 | 2018-11-29 3:59 | 2018-11-29 9:49 | MySQL Server: Replication | Not a Bug (1946 days) | S1 | 5.7.23 | Any | Any | Some commit may not written to binlog |
54093 | 2010-05-31 3:16 | 2018-11-22 13:28 | MySQL Server: Replication | Not a Bug (1953 days) | S3 | 5.5 | Any | Any | The size limitation of a row event is not controlled by max_packet_size |
89959 | 2018-03-08 10:59 | 2019-04-12 9:08 | MySQL Server: Replication | Not a Bug (1956 days) | S2 | 8.0.4 | Any | Any | Replication fails when users are created using caching_sha2_password |
92878 | 2018-10-22 9:44 | 2018-10-22 9:56 | MySQL Server: Replication | Not a Bug (1984 days) | S3 | 5.5.61 | Ubuntu | Any | CHANGE MASTER TO MASTER_DELAY |
76341 | 2015-03-16 17:10 | 2018-08-22 17:21 | MySQL Server: Replication | Not a Bug (2045 days) | S2 | 5.7.6 | Linux (3.10.0-123.9.3.el7.x86_64) | Any | Replication with GTID (no binlog) fails - 'Binary log is not open' |
91940 | 2018-08-09 2:31 | 2018-08-16 12:27 | MySQL Server: Replication | Not a Bug (2051 days) | S3 | 5.7.17 | CentOS (Linux 3.10.0-229.el7.x86_64) | Any | MySQL 5.7.17 abnormal crash |
Showing 1-30 of 232 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |