Showing all 16 (Edit, Save, CSV, Feed) |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
80502 | 2016-02-25 2:16 | 2016-09-24 19:13 | MySQL Server: Group Replication | Duplicate (2743 days) | S2 | 0.7 lab, 5.7.14-labs-gr080 | Oracle Linux | Any | Data Inconsistency with Truncate session along with INSERT/UPDATE/SELECTsession |
82275 | 2016-07-18 21:21 | 2016-07-18 21:25 | MySQL Server: Group Replication | Duplicate (2811 days) | S3 | 0.7.0-labs | Any | Any | Crash in accept_tcp |
84710 | 2017-01-30 8:45 | 2017-11-21 10:21 | MySQL Server: Group Replication | Duplicate (2320 days) | S1 | 5.7.17 | Any | Any | group replication does not respect localhost IP |
85364 | 2017-03-08 8:06 | 2017-05-09 14:49 | MySQL Server: Group Replication | Duplicate (2516 days) | S3 | 5.7.11, 5.7.17 | CentOS | Any | handle_fatal_signal (sig=6) in Gtid_table_access_context::init |
88163 | 2017-10-20 7:03 | 2018-04-12 5:22 | MySQL Server: Group Replication | Duplicate (2178 days) | S3 | 5.7.20 | Debian (Debian 8) | Any | /usr/sbin/mysqld --initialize-insecure hang with group replication enabled |
89141 | 2018-01-08 22:07 | 2018-04-11 16:23 | MySQL Server: Group Replication | Duplicate (2179 days) | S2 | 5.7.20,8.0.3 | Any | Any | Error in Group Replication caused by bad Write Set tracking. |
89194 | 2018-01-11 19:14 | 2018-04-11 16:23 | MySQL Server: Group Replication | Duplicate (2179 days) | S2 | 5.7.20, 8.0.3 | Any | Any | Wrong certification lead to data inconsistency and GR breakage. |
102075 | 2020-12-26 9:25 | 2020-12-28 15:01 | MySQL Server: Group Replication | Duplicate (1187 days) | S2 | 5.7.29 | CentOS (CentOS Linux release 7.5.1804 (Core) ) | x86 (Intel(R) Xeon(R) CPU E5-2640 v4 @ 2.40GHz) | network and server is ok, but GR node been unreachable |
103421 | 2021-04-22 8:22 | 2021-07-15 8:46 | MySQL Server: Group Replication | Duplicate (988 days) | S2 | CentOS | Any | DDL in group replication cluster also if online cause full stop of write operati | |
107254 | 2022-05-10 12:29 | 2022-05-10 12:45 | MySQL Server: Group Replication | Duplicate (689 days) | S1 | MySQL 8.0.xx | Linux (Centos 7/8) | Any | MySQL Group Replication slave applier breaks due to parallel replication |
108291 | 2022-08-26 2:55 | 2022-09-06 14:20 | MySQL Server: Group Replication | Duplicate (570 days) | S3 | 8.0.30 | Any | Any | There is a problem for foreign key in Single-Primary Mode MGR environment |
109144 | 2022-11-19 5:03 | 2022-11-21 14:26 | MySQL Server: Group Replication | Duplicate (494 days) | S2 | 8.0.31 | Any | Any | GCS_DEBUG_TRACE lacks timestamps |
113548 | 2024-01-04 7:38 | 2024-01-09 9:30 | MySQL Server: Group Replication | Duplicate (80 days) | S2 | 8.0.34-26 | Any | Any | Cloning failing in Mysql Group replication |
84313 | 2016-12-22 9:32 | 2017-06-26 5:02 | MySQL Server: Group Replication | Duplicate (2636 days) | S3 | 5.7.17 | Debian | Any | mysql group replication should not rely on hostnames |
92916 | 2018-10-24 2:06 | 2018-10-31 15:54 | MySQL Server: Group Replication | Duplicate (1976 days) | S1 | 5.7.22 | Red Hat (7) | Any | network partition, cause only one online situation |
105748 | 2021-11-30 11:47 | 2021-12-13 13:07 | MySQL Server: Group Replication | Duplicate (837 days) | S2 | Any | Any | Why is group_replication_consistency = AFTER crashing a Group Replication cluste |
Showing all 16 (Edit, Save, CSV, Feed) |