Showing 1-30 of 145 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
86979 | 2017-07-07 7:11 | 2018-04-11 16:07 | MySQL Server: Group Replication | Closed (2178 days) | S3 | mysql5.7.18 | Ubuntu | Any | group replicat master automatically quit |
95306 | 2019-05-08 17:20 | 2019-07-25 8:40 | MySQL Server: Group Replication | Closed (1774 days) | S3 | 8.0.17 | Any | Any | _get_communication_protocol() fails if one or more members are RECOVERING |
76876 | 2015-04-28 18:53 | 2016-04-27 15:03 | MySQL Server: Group Replication | Closed (3181 days) | S3 | 0.4.0 | Any | Any | --transaction-write-set-extraction is considering non unique and NULL keys |
92454 | 2018-09-17 7:16 | 2018-11-02 14:34 | MySQL Server: Group Replication | Closed (1973 days) | S3 | 8.0.11-commercial | CentOS | Any | [GCS] Error pushing message into group communication engine |
81565 | 2016-05-24 8:45 | 2016-05-24 8:48 | MySQL Server: Group Replication | Closed (2865 days) | S3 | Ubuntu (15.10) | Any | 2 of 3 GR nodes down, but replication_group_members reports otherwise | |
90217 | 2018-03-26 15:07 | 2019-01-08 15:13 | MySQL Server: Group Replication | Closed (1906 days) | S1 | 8.0 | Any | Any | Add IPv6 support for Group Replication |
104980 | 2021-09-18 1:33 | 2022-12-22 5:15 | MySQL Server: Group Replication | Closed (500 days) | S2 | 8.0.26 | Any | Any | After secondary node is killed, it can not rejoined |
91870 | 2018-08-02 11:33 | 2019-01-22 14:00 | MySQL Server: Group Replication | Closed (1933 days) | S3 | 8.0.13 | Any | Any | ALL MEMBERS ARE EXITED FROM GR WHEN 1/4 NODE TRIED TO REJOIN AFTER network drop |
93348 | 2018-11-26 15:04 | 2019-07-25 8:31 | MySQL Server: Group Replication | Closed (1933 days) | S3 | 5.7.21 | Any | Any | Always log the use of group_replication_allow_local_disjoint_gtids_join |
92376 | 2018-09-12 8:59 | 2019-01-22 13:59 | MySQL Server: Group Replication | Closed (1948 days) | S3 | 5.7.22 | Any | Any | Analyze and backport Bug#28365855 to 5.7 |
88602 | 2017-11-22 9:18 | 2018-05-31 14:49 | MySQL Server: Group Replication | Closed (2227 days) | S2 | 9.0.0 | Any | Any | Assert `! is_set()' at sql_error.cc:402 if set var executed on S2 post S1 killed |
91747 | 2018-07-21 9:15 | 2019-01-22 14:04 | MySQL Server: Group Replication | Closed (1924 days) | S2 | 8.0.14 | Any | Any | ASSERT `!is_set()' at sql_error.cc:379 upon STOP G.R. in ERRORed member |
87759 | 2017-09-14 15:16 | 2018-04-12 5:23 | MySQL Server: Group Replication | Closed (2296 days) | S3 | 8.0.4 | Any | Any | Assert `server_engine_initialized()' at delayed_plugin_initialization.cc:167 |
89060 | 2017-12-26 19:28 | 2018-05-31 14:54 | MySQL Server: Group Replication | Closed (2227 days) | S3 | 8.0.11 | Any | Any | ASSERT ON SET GLOBAL GTID_MODE ON AN OFFLINE (READ_ONLY) MEMBER |
78749 | 2015-10-08 6:25 | 2015-12-03 14:05 | MySQL Server: Group Replication | Closed (3038 days) | S1 | 0.5.0-dmr | Ubuntu (14.04) | Any | Assertion `!flags.finalized' failed with group replication plugin |
113838 | 2024-01-31 19:24 | 2024-02-14 0:27 | MySQL Server: Group Replication | Closed (43 days) | S3 | 8.0+ | Any | Any | Async connection failover prevents failed Group Replication member rejoin |
86359 | 2017-05-17 14:53 | 2017-11-08 10:27 | MySQL Server: Group Replication | Closed (2386 days) | S3 | 5.7.18 | Any | Any | Avoid setting group_replication_force_members in a partition that holds majority |
93130 | 2018-11-08 18:58 | 2019-01-22 13:54 | MySQL Server: Group Replication | Closed (1948 days) | S3 | 5.7.25 | Any | Any | Backport Bug#28443958 to mysql-5.7 |
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 |
84794 | 2017-02-02 13:36 | 2017-11-08 9:42 | MySQL Server: Group Replication | Closed (2332 days) | S3 | 5.7.17 | Any | Any | Cannot kill query inside GR |
94004 | 2019-01-22 15:37 | 2019-02-19 12:17 | MySQL Server: Group Replication | Closed (1886 days) | S2 | 8.0.14 | Debian (Stretch) | x86 (amd64) | Cannot setup replication without ipv6 since 8.0.14 |
84733 | 2017-01-31 9:15 | 2017-06-21 11:32 | MySQL Server: Group Replication | Closed (2553 days) | S3 | 5.7.17 | Any | Any | Cannot Start GR with super_read_only=1 |
93027 | 2018-10-31 12:43 | 2020-01-20 9:44 | MySQL Server: Group Replication | Closed (1744 days) | S3 | 8.0.14 | Any | Any | Centralize the leave on error code for all components |
90986 | 2018-05-23 9:40 | 2018-11-06 16:58 | MySQL Server: Group Replication | Closed (2030 days) | S3 | 5.7.23 | Any | Any | Config issue makes server skips own details in ER_GRP_RPL_MEMBER_CHANGE msg |
84337 | 2016-12-26 8:50 | 2017-07-11 11:52 | MySQL Server: Group Replication | Closed (2452 days) | S2 | mysql 5.7.17 | Any | Any | Configure mgr with out root user encounter an error |
86858 | 2017-06-29 3:19 | 2017-11-08 10:32 | MySQL Server: Group Replication | Closed (2393 days) | S2 | 5.7.18 | Any | Any | Confusing GR error message: check credentials, but issue is hostnanme resolving |
90671 | 2018-04-27 20:40 | 2019-07-25 8:26 | MySQL Server: Group Replication | Closed (1885 days) | S3 | 5.7 | Any | Any | Connection error messages not shown in gr. gr_recovery_connection_options wrong |
94854 | 2019-04-01 13:57 | 2019-06-19 8:17 | MySQL Server: Group Replication | Closed (1744 days) | S3 | Any | Any | Contribution: fixed broken GCS error message | |
105938 | 2021-12-20 10:18 | 2022-08-29 14:46 | MySQL Server: Group Replication | Closed (577 days) | S3 | 8.0.27 | Any | Any | COUNT_TRANSACTIONS_REMOTE_IN_APPLIER_QUEUE count abnormal |
88182 | 2017-10-23 7:15 | 2018-02-01 14:03 | MySQL Server: Group Replication | Closed (2297 days) | S3 | 8.0.4 | Any | Any | crash during shutdown when start GR executed if max connections already opened |
Showing 1-30 of 145 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |