Showing 1-30 of 65 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
90443 | 2018-04-16 6:24 | 2018-04-17 15:12 | Shell AdminAPI InnoDB Cluster / ReplicaSet | Can't repeat (2198 days) | S3 | 8.0.4 | Any | Any | mysqlsh using 100% cpu after tty is gone |
83237 | 2016-10-01 21:21 | 2020-01-19 2:21 | MySQL Router | Can't repeat (2534 days) | S1 | v2.1.0 | Any | Any | mysqlrouter connects to wrong metadata server (a partitioned node) |
84792 | 2017-02-02 12:49 | 2017-05-03 13:18 | MySQL Server: Group Replication | Can't repeat (2547 days) | S3 | 5.7.17 | Any | Any | Idle GR Cluster: Member CPU hog |
84796 | 2017-02-02 14:13 | 2020-03-04 10:45 | MySQL Server: Group Replication | Closed (1511 days) | S3 | 8.0.4 | Any | Any | GR Member status is wrong |
81546 | 2016-05-23 15:16 | 2020-05-22 12:10 | MySQL Workbench: Migration | Closed (1526 days) | S3 | 6.3.6, 8.0.19 | Windows | Any | Workbench Migration weird error when trying to connect using an ODBC FreeTDS |
84729 | 2017-01-31 8:39 | 2019-10-30 12:48 | MySQL Server: Group Replication | Closed (1637 days) | S4 | 5.7.17 | Any | Any | Group Replication: Block Reads On Partitioned Nodes |
84784 | 2017-02-02 3:06 | 2019-07-07 6:39 | MySQL Server: Group Replication | Closed (1854 days) | S2 | 5.7.17, 8.0.4 | Any | Any | Group Replication nodes do not rejoin cluster after network connectivity issues |
84631 | 2017-01-24 1:38 | 2019-01-03 11:45 | MySQL Server: Documentation | Closed (1937 days) | S3 | 5.7 | Any | Any | Group Replication Installation Documentation |
90794 | 2018-05-08 15:37 | 2018-11-19 16:05 | MySQL Server: Group Replication | Closed (1982 days) | S2 | 5.7.22 | Any | Any | GR 5.7.22 not compatible with earlier versions due to lower_case_table_names |
90461 | 2018-04-17 4:58 | 2018-11-22 10:19 | MySQL Server: Group Replication | Closed (1985 days) | S4 | 8.0.4 | Any | Any | Change group_replication_single_primary_mode online |
90457 | 2018-04-16 22:28 | 2018-08-09 14:57 | MySQL Server: Group Replication | Closed (2084 days) | S2 | 8.0.4 | Any | Any | mysqld crash with ctrl-c/z'ed `START GROUP_REPLICATION` |
90483 | 2018-04-17 23:54 | 2018-08-07 8:57 | MySQL Server: Group Replication | Closed (2086 days) | S3 | 5.7.21, 8.0.4 | CentOS | Any | dns based seeds resolving to itself causes GR to not start |
90438 | 2018-04-14 1:58 | 2018-05-21 10:46 | Shell AdminAPI InnoDB Cluster / ReplicaSet | Closed (2164 days) | S3 | 8.0.4, 5.7.21 | CentOS (7) | Any | MySQL InnoDB Cluster (mysql-shell AdminAPI) fails to rejoin instances |
71658 | 2014-02-10 16:08 | 2018-01-18 13:20 | MySQL Server: Charsets | Closed (2287 days) | S3 | 5.6.15, 5.6.16, 5.5.36, 5.7.14 | Any | Any | Comparison of DATE_ADD(null...) with NOW() Fails in 5.6 |
88733 | 2017-12-01 18:08 | 2017-12-03 18:30 | MySQL Server: XA transactions | Closed (2333 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 (2333 days) | S3 | 5.7.19 | Any | Any | XA transactions with binlog_format=STATEMENT do not get errors or warnings |
84794 | 2017-02-02 13:36 | 2017-11-08 9:42 | MySQL Server: Group Replication | Closed (2358 days) | S3 | 5.7.17 | Any | Any | Cannot kill query inside GR |
84798 | 2017-02-02 14:32 | 2017-09-22 15:41 | MySQL Server: Group Replication | Closed (2405 days) | S3 | 5.7.17 | Any | Any | Group Replication can use some verbosity in the error log |
84731 | 2017-01-31 8:56 | 2017-09-18 10:30 | MySQL Server: Group Replication | Closed (2409 days) | S3 | 5.7.17 | Any | Any | Group Replication: mysql client connections hang during group replication start |
85175 | 2017-02-24 15:28 | 2017-08-04 20:11 | MySQL Server: Documentation | Closed (2454 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 (2471 days) | S3 | 2.1.3 | Linux (centos 7) | Any | mysqlrouter does not start with default mysqlrouter --bootstrap |
84728 | 2017-01-31 8:22 | 2017-07-11 11:08 | MySQL Server: Group Replication | Closed (2478 days) | S2 | 5.7.17 | Any | Any | Not Possible To Avoid MySQL From Starting When GR Cannot Start |
84795 | 2017-02-02 13:44 | 2017-11-08 9:40 | MySQL Server: Group Replication | Closed (2490 days) | S3 | 5.7.17 | Any | Any | STOP GROUP_REPLICATION sets super_read_only=off |
84727 | 2017-01-31 8:16 | 2017-06-26 15:59 | MySQL Server: Group Replication | Closed (2493 days) | S2 | 5.7.17 | Any | Any | GR: Partitioned Node Should Get Updated Status and not accept writes |
84785 | 2017-02-02 3:38 | 2017-06-09 9:37 | MySQL Server: Group Replication | Closed (2510 days) | S2 | 5.7.17 | Any | Any | Prevent Large Transactions in Group Replication |
84733 | 2017-01-31 9:15 | 2017-06-21 11:32 | MySQL Server: Group Replication | Closed (2579 days) | S3 | 5.7.17 | Any | Any | Cannot Start GR with super_read_only=1 |
83207 | 2016-09-29 14:36 | 2017-03-24 13:17 | MySQL Server: Document Store: MySQL Shell | Closed (2587 days) | S3 | 5.7.15 Preview MIC | Any | Any | mysqlsh: dba.validateInstance() gives strange errors and outputs data twice |
84674 | 2017-01-25 22:05 | 2017-02-16 10:59 | MySQL Server: Group Replication | Closed (2623 days) | S3 | 5.7.latest | Any | Any | Having an unresolvable hostname in group_repl should not block group replication |
81672 | 2016-06-01 9:04 | 2016-09-21 15:11 | MySQL Server: Optimizer | Closed (2771 days) | S3 | 5.6 | Any | Any | Less optimal index is chosen, index length does impact cost |
80962 | 2016-04-05 15:57 | 2016-07-01 10:38 | MySQL Server: Replication | Closed (2853 days) | S3 | 5.7 | Any | Any | Replication does not work when @@GLOBAL.SERVER_UUID is missing on the master |
Showing 1-30 of 65 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |