« Show Previous 30 Entries | Showing 31-60 of 65 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
84798 | 2017-02-02 14:32 | 2017-09-22 15:41 | MySQL Server: Group Replication | Closed (2380 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 (2612 days) | S3 | 5.7.17 | Any | Any | mysqldump --single-transaction uses savepoints, does not work with GR |
84785 | 2017-02-02 3:38 | 2017-06-09 9:37 | MySQL Server: Group Replication | Closed (2485 days) | S2 | 5.7.17 | Any | Any | Prevent Large Transactions in Group Replication |
84792 | 2017-02-02 12:49 | 2017-05-03 13:18 | MySQL Server: Group Replication | Can't repeat (2522 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 (2333 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 (2465 days) | S3 | 5.7.17 | Any | Any | STOP GROUP_REPLICATION sets super_read_only=off |
86149 | 2017-05-01 17:00 | 2022-01-21 2:55 | MySQL Server: Group Replication | No Feedback (2493 days) | S3 | 5.7.17 | CentOS | Any | MySQL Group Replication Crash - Failing assertion: !cursor->index->is_committed |
84784 | 2017-02-02 3:06 | 2019-07-07 6:39 | MySQL Server: Group Replication | Closed (1829 days) | S2 | 5.7.17, 8.0.4 | Any | Any | Group Replication nodes do not rejoin cluster after network connectivity issues |
87208 | 2017-07-26 14:05 | 2017-07-31 12:24 | MySQL Server: Group Replication | Not a Bug (2433 days) | S3 | 5.7.18 | Any | Any | Flow control mechanism does not prevent nodes from lagging further behind |
88734 | 2017-12-01 18:11 | 2017-12-03 18:30 | MySQL Server: XA transactions | Closed (2308 days) | S3 | 5.7.19 | Any | Any | XA transactions with binlog_format=STATEMENT do not get errors or warnings |
88733 | 2017-12-01 18:08 | 2017-12-03 18:30 | MySQL Server: XA transactions | Closed (2308 days) | S3 | 5.7.19 | Any | Any | XA trx with binlog_format=MIXED writes binlogs in SBR |
88358 | 2017-11-04 2:32 | 2018-08-26 20:45 | MySQL Server: Replication | Duplicate (2334 days) | S1 | 5.7.19, 5.7.20 | Any | Any | Break replication by running some XA ROLLBACK statements |
90483 | 2018-04-17 23:54 | 2018-08-07 8:57 | MySQL Server: Group Replication | Closed (2061 days) | S3 | 5.7.21, 8.0.4 | CentOS | Any | dns based seeds resolving to itself causes GR to not start |
90794 | 2018-05-08 15:37 | 2018-11-19 16:05 | MySQL Server: Group Replication | Closed (1957 days) | S2 | 5.7.22 | Any | Any | GR 5.7.22 not compatible with earlier versions due to lower_case_table_names |
80084 | 2016-01-20 19:49 | 2020-01-03 1:00 | MySQL Server: Replication | No Feedback (1548 days) | S3 | 5.7.9, 5.6.22 | Any | Any | Seconds_behind_master distorted because of verbatim master's FDE in relaylog |
84674 | 2017-01-25 22:05 | 2017-02-16 10:59 | MySQL Server: Group Replication | Closed (2598 days) | S3 | 5.7.latest | Any | Any | Having an unresolvable hostname in group_repl should not block group replication |
81592 | 2016-05-25 10:20 | 2016-05-25 11:41 | MySQL Workbench: Migration | Verified (2865 days) | S3 | 6.3.6 | Any | Any | Workbench Migrate using ODBC from Sybase does not migrate default column values. |
81589 | 2016-05-25 9:59 | 2016-05-25 11:41 | MySQL Workbench: Migration | Verified (2865 days) | S3 | 6.3.6 | Any | Any | Migration From Sybase using FreeTDS: CREATE TABLEs are not properly converted |
81568 | 2016-05-24 9:23 | 2016-05-24 10:34 | MySQL Workbench | Verified (2866 days) | S3 | 6.3.6 | Any | Any | Workbench Preferences Pane Layout not wrapped |
81562 | 2016-05-24 8:12 | 2016-05-25 11:35 | MySQL Workbench: Migration | Verified (2865 days) | S3 | 6.3.6 | Any | Any | Workbench Migrate from Sybase to MySQL does not copy primary keys |
81555 | 2016-05-23 21:38 | 2016-05-24 9:27 | MySQL Workbench: Migration | Not a Bug (2866 days) | S3 | 6.3.6 | Any | Any | Workbench Migration Fails |
81554 | 2016-05-23 21:22 | 2016-05-25 11:34 | MySQL Workbench: Migration | Verified (2865 days) | S3 | 6.3.6 | Any | Any | Data Migration Wizard: using [] quoted objects with Sybase fails on max 28 bytes |
81545 | 2016-05-23 15:02 | 2016-05-25 11:31 | MySQL Workbench: Migration | Verified (2865 days) | S3 | 6.3.6 | Any | Any | Data Migration: Changed sybase `getTriggerNames` to singlequoted search on 'TR' |
81546 | 2016-05-23 15:16 | 2020-05-22 12:10 | MySQL Workbench: Migration | Closed (1501 days) | S3 | 6.3.6, 8.0.19 | Windows | Any | Workbench Migration weird error when trying to connect using an ODBC FreeTDS |
90562 | 2018-04-23 6:50 | 2018-04-26 16:02 | MySQL Server: Document Store: MySQL Shell | Duplicate (2164 days) | S3 | 8.0.11 | Any | Any | mysqlsh: weird sql error |
84796 | 2017-02-02 14:13 | 2020-03-04 10:45 | MySQL Server: Group Replication | Closed (1486 days) | S3 | 8.0.4 | Any | Any | GR Member status is wrong |
90485 | 2018-04-18 2:35 | 2018-05-22 18:18 | MySQL Server: Group Replication | Verified (2138 days) | S3 | 8.0.4 | Any | Any | Ignore group_replication_group_seeds nodes if they are not primary/active |
90484 | 2018-04-18 1:33 | 2019-03-09 15:39 | MySQL Server: Group Replication | Verified (1847 days) | S4 | 8.0.4 | CentOS (7) | Any | No (easy) way to know if a GR node is writeable or not |
90461 | 2018-04-17 4:58 | 2018-11-22 10:19 | MySQL Server: Group Replication | Closed (1960 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 (2059 days) | S2 | 8.0.4 | Any | Any | mysqld crash with ctrl-c/z'ed `START GROUP_REPLICATION` |
« Show Previous 30 Entries | Showing 31-60 of 65 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |