| Showing 1-30 of 65 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 83237 | 2016-10-01 21:21 | 2020-01-19 2:21 | MySQL Router | Can't repeat (2530 days) | S1 | v2.1.0 | Any | Any | mysqlrouter connects to wrong metadata server (a partitioned node) |
| 88358 | 2017-11-04 2:32 | 2018-08-26 20:45 | MySQL Server: Replication | Duplicate (2355 days) | S1 | 5.7.19, 5.7.20 | Any | Any | Break replication by running some XA ROLLBACK statements |
| 90794 | 2018-05-08 15:37 | 2018-11-19 16:05 | MySQL Server: Group Replication | Closed (1978 days) | S2 | 5.7.22 | Any | Any | GR 5.7.22 not compatible with earlier versions due to lower_case_table_names |
| 84727 | 2017-01-31 8:16 | 2017-06-26 15:59 | MySQL Server: Group Replication | Closed (2489 days) | S2 | 5.7.17 | Any | Any | GR: Partitioned Node Should Get Updated Status and not accept writes |
| 84728 | 2017-01-31 8:22 | 2017-07-11 11:08 | MySQL Server: Group Replication | Closed (2474 days) | S2 | 5.7.17 | Any | Any | Not Possible To Avoid MySQL From Starting When GR Cannot Start |
| 83234 | 2016-10-01 20:06 | 2016-10-10 14:57 | MySQL Server: Replication | Verified (2755 days) | S2 | 5.7.15-labs-gr090-log | Any | Any | RESET SLAVE ALL during SUPER_READ_ONLY breaks replication setup |
| 84784 | 2017-02-02 3:06 | 2019-07-07 6:39 | MySQL Server: Group Replication | Closed (1850 days) | S2 | 5.7.17, 8.0.4 | Any | Any | Group Replication nodes do not rejoin cluster after network connectivity issues |
| 84785 | 2017-02-02 3:38 | 2017-06-09 9:37 | MySQL Server: Group Replication | Closed (2506 days) | S2 | 5.7.17 | Any | Any | Prevent Large Transactions in Group Replication |
| 62557 | 2011-09-27 20:52 | 2012-09-07 13:59 | MySQL Server: Replication | Closed (4242 days) | S2 | 5.1, 5.5 | Any | Any | SHOW SLAVE STATUS gives wrong output with master-master and using SET uservars |
| 90457 | 2018-04-16 22:28 | 2018-08-09 14:57 | MySQL Server: Group Replication | Closed (2080 days) | S2 | 8.0.4 | Any | Any | mysqld crash with ctrl-c/z'ed `START GROUP_REPLICATION` |
| 84796 | 2017-02-02 14:13 | 2020-03-04 10:45 | MySQL Server: Group Replication | Closed (1507 days) | S3 | 8.0.4 | Any | Any | GR Member status is wrong |
| 84674 | 2017-01-25 22:05 | 2017-02-16 10:59 | MySQL Server: Group Replication | Closed (2619 days) | S3 | 5.7.latest | Any | Any | Having an unresolvable hostname in group_repl should not block group replication |
| 90562 | 2018-04-23 6:50 | 2018-04-26 16:02 | MySQL Server: Document Store: MySQL Shell | Duplicate (2185 days) | S3 | 8.0.11 | Any | Any | mysqlsh: weird sql error |
| 90485 | 2018-04-18 2:35 | 2018-05-22 18:18 | MySQL Server: Group Replication | Verified (2159 days) | S3 | 8.0.4 | Any | Any | Ignore group_replication_group_seeds nodes if they are not primary/active |
| 84731 | 2017-01-31 8:56 | 2017-09-18 10:30 | MySQL Server: Group Replication | Closed (2405 days) | S3 | 5.7.17 | Any | Any | Group Replication: mysql client connections hang during group replication start |
| 84733 | 2017-01-31 9:15 | 2017-06-21 11:32 | MySQL Server: Group Replication | Closed (2575 days) | S3 | 5.7.17 | Any | Any | Cannot Start GR with super_read_only=1 |
| 90483 | 2018-04-17 23:54 | 2018-08-07 8:57 | MySQL Server: Group Replication | Closed (2082 days) | S3 | 5.7.21, 8.0.4 | CentOS | Any | dns based seeds resolving to itself causes GR to not start |
| 84792 | 2017-02-02 12:49 | 2017-05-03 13:18 | MySQL Server: Group Replication | Can't repeat (2543 days) | S3 | 5.7.17 | Any | Any | Idle GR Cluster: Member CPU hog |
| 84794 | 2017-02-02 13:36 | 2017-11-08 9:42 | MySQL Server: Group Replication | Closed (2354 days) | S3 | 5.7.17 | Any | Any | Cannot kill query inside GR |
| 84795 | 2017-02-02 13:44 | 2017-11-08 9:40 | MySQL Server: Group Replication | Closed (2486 days) | S3 | 5.7.17 | Any | Any | STOP GROUP_REPLICATION sets super_read_only=off |
| 90438 | 2018-04-14 1:58 | 2018-05-21 10:46 | Shell AdminAPI InnoDB Cluster / ReplicaSet | Closed (2160 days) | S3 | 8.0.4, 5.7.21 | CentOS (7) | Any | MySQL InnoDB Cluster (mysql-shell AdminAPI) fails to rejoin instances |
| 84798 | 2017-02-02 14:32 | 2017-09-22 15:41 | MySQL Server: Group Replication | Closed (2401 days) | S3 | 5.7.17 | Any | Any | Group Replication can use some verbosity in the error log |
| 84799 | 2017-02-02 14:36 | 2017-02-02 14:46 | MySQL Server: mysqldump Command-line Client | Duplicate (2633 days) | S3 | 5.7.17 | Any | Any | mysqldump --single-transaction uses savepoints, does not work with GR |
| 85175 | 2017-02-24 15:28 | 2017-08-04 20:11 | MySQL Server: Documentation | Closed (2450 days) | S3 | 5.7 | CentOS | Any | Changing security/limits.conf does not apply on systemd systems |
| 86050 | 2017-04-23 22:22 | 2017-07-18 15:49 | MySQL Router | Closed (2467 days) | S3 | 2.1.3 | Linux (centos 7) | Any | mysqlrouter does not start with default mysqlrouter --bootstrap |
| 86149 | 2017-05-01 17:00 | 2022-01-21 2:55 | MySQL Server: Group Replication | No Feedback (2514 days) | S3 | 5.7.17 | CentOS | Any | MySQL Group Replication Crash - Failing assertion: !cursor->index->is_committed |
| 87208 | 2017-07-26 14:05 | 2017-07-31 12:24 | MySQL Server: Group Replication | Not a Bug (2454 days) | S3 | 5.7.18 | Any | Any | Flow control mechanism does not prevent nodes from lagging further behind |
| 90443 | 2018-04-16 6:24 | 2018-04-17 15:12 | Shell AdminAPI InnoDB Cluster / ReplicaSet | Can't repeat (2194 days) | S3 | 8.0.4 | Any | Any | mysqlsh using 100% cpu after tty is gone |
| 88733 | 2017-12-01 18:08 | 2017-12-03 18:30 | MySQL Server: XA transactions | Closed (2329 days) | S3 | 5.7.19 | Any | Any | XA trx with binlog_format=MIXED writes binlogs in SBR |
| 88734 | 2017-12-01 18:11 | 2017-12-03 18:30 | MySQL Server: XA transactions | Closed (2329 days) | S3 | 5.7.19 | Any | Any | XA transactions with binlog_format=STATEMENT do not get errors or warnings |
| Showing 1-30 of 65 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
