Showing 1-30 of 42 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
93781 | 2019-01-02 13:27 | 2019-01-02 14:31 | MySQL Cluster: Cluster (NDB) storage engine | Not a Bug (1913 days) | S2 | CentOS | Any | Memory usage statistics in ndbinfo.memoryusage table are way off | |
90765 | 2018-05-05 21:23 | 2018-06-08 1:00 | MySQL Cluster: NDB API | No Feedback (2122 days) | S2 | 5.7.8 | CentOS | Any | api node crashes under heavy connect disconnect |
90761 | 2018-05-05 8:10 | 2018-05-14 15:50 | MySQL Cluster: NDB API | Can't repeat (2146 days) | S3 | 7.5.8 | CentOS | Any | api node crashes under heavy connect disconnect |
106096 | 2022-01-07 9:08 | 2022-02-08 1:00 | MySQL Cluster: Replication | No Feedback (781 days) | S3 | 5.7.23 | CentOS (CentOS Linux release 7.6.1810) | Any | master's command of "reset master" perhaps makes slave/dr gtid gap |
86499 | 2017-05-29 13:13 | 2017-05-31 14:35 | MySQL Cluster: Replication | Not a Bug (2494 days) | S1 | 5.1.66 | CentOS (release 6.2) | Any | the slave i/O thread stops because master and slave have equal mysql error ids; |
93532 | 2018-12-09 21:18 | 2018-12-12 21:06 | MySQL Cluster: Disk Data | Can't repeat (1934 days) | S1 | 7.5.8 | CentOS | Any | Caused by error 7200: LCP fragment scan watchdog detected a problem |
82048 | 2016-06-29 9:54 | 2016-06-29 13:50 | MySQL Cluster: Cluster/J | Closed (2830 days) | S2 | 7.2.23 | CentOS | Any | MySQL Cluster SQL Node cant connect to cluster |
101890 | 2020-12-07 12:10 | 2020-12-10 9:37 | MySQL Cluster: Cluster (NDB) storage engine | Not a Bug (1205 days) | S3 | 7.5.20 | CentOS | Any | mysql_upgrade from MySQL-Cluster 7.4.27 to 7.5.20 crashes SQL node |
100675 | 2020-08-28 11:03 | 2020-10-22 19:06 | MySQL Cluster: Cluster (NDB) storage engine | Can't repeat (1254 days) | S3 | mysql-5.6.28 ndb-7.4.10 | CentOS | Any | NDB data node disconnted |
98895 | 2020-03-10 17:28 | 2020-11-06 5:02 | MySQL Cluster: Cluster (NDB) storage engine | Closed (1239 days) | S2 | mysql-8.0.19 ndb-8.0.19 | CentOS (7) | Any | mysql 8 ndbcluster distributed privileges failure |
97668 | 2019-11-17 6:13 | 2019-11-19 13:42 | MySQL Cluster: Cluster (NDB) storage engine | Can't repeat (1592 days) | S1 | mysql-5.7.23 ndb-7.6.12 | CentOS | Any | (urgent) Cluster crashed after alter table |
78927 | 2015-10-22 17:44 | 2016-09-02 16:24 | MySQL Cluster: Cluster (NDB) storage engine | Verified (3069 days) | S2 | 5.6.23-ndb-7.4.5-cluster-gpl | CentOS (may be other too) | Any | Can't create index on big columns: Specified key was too long |
92434 | 2018-09-15 9:48 | 2018-10-10 0:23 | MySQL Cluster: Cluster (NDB) storage engine | Duplicate (1997 days) | S2 | 7.6.6 | CentOS (7) | Any | NDB node keep crashing due to Backup.cpp bug |
87610 | 2017-08-30 14:49 | 2017-10-17 16:38 | MySQL Cluster: Cluster (NDB) storage engine | Verified (2355 days) | S2 | 7.5.4 | CentOS | Any | Got error 741 'Unsupported alter table' from NDBCLUSTER |
79179 | 2015-11-09 1:31 | 2020-11-08 13:13 | MySQL Cluster: Cluster (NDB) storage engine | Verified (3063 days) | S2 | 7.4.7 | CentOS (6.5 x64) | Any | bit data type was not full supported by MySQL cluster |
81360 | 2016-05-10 4:34 | 2016-06-07 11:41 | MySQL Cluster: Cluster (NDB) storage engine | Can't repeat (2852 days) | S2 | 7.4.8 | CentOS (CentOS 7) | Any | there is memory crash issue in mysql-5.6.27 ndb-7.4.8 |
81506 | 2016-05-19 12:08 | 2016-05-24 19:34 | MySQL Cluster: Cluster (NDB) storage engine | Not a Bug (2866 days) | S1 | mysql-cluster-gpl-7.4.11-linux-glibc2.5- | CentOS (7.0) | Any | ndbd always be in "starting" state after i run it as "--initial" |
82514 | 2016-08-09 14:13 | 2016-09-08 6:35 | MySQL Cluster: Cluster (NDB) storage engine | Can't repeat (2759 days) | S3 | mysql Ver 14.14 Distrib 5.6.17-ndb-7.3. | CentOS (release 6.5 (Final) x64) | Any | Data Nodes Randomly Crashing |
82970 | 2016-09-13 13:43 | 2016-11-06 1:00 | MySQL Cluster: Cluster (NDB) storage engine | No Feedback (2701 days) | S3 | 5.6.25-ndb-7.4.7-cluster-gpl | CentOS (6.6) | Any | MYSQL cluster downtime during data backup with mysqldump |
83424 | 2016-10-18 9:58 | 2016-11-20 1:00 | MySQL Cluster: Cluster (NDB) storage engine | No Feedback (2687 days) | S3 | mysql-5.6.17 ndb-7.3.5 | CentOS | Any | ndbmtd crash |
83596 | 2016-10-28 8:06 | 2016-11-21 13:51 | MySQL Cluster: Cluster (NDB) storage engine | Verified (2685 days) | S2 | 5.6.27-ndb-7.4.8-cluster-gpl | CentOS (CentOS release 6.4) | Any | select with group_concat will resturn wrong result of bit fields |
84135 | 2016-12-09 2:01 | 2016-12-21 1:08 | MySQL Cluster: Cluster (NDB) storage engine | Not a Bug (2655 days) | S2 | mysql-5.7.16 ndb-7.5.4 | CentOS (CentOS Linux release 7.2.1511 (Core)) | Any | when create table, it thow an exception "Could not connect to storage engine" |
85584 | 2017-03-22 15:49 | 2017-04-25 18:08 | MySQL Cluster: Cluster (NDB) storage engine | Not a Bug (2530 days) | S2 | ndb-7.4.7 | CentOS (6.6) | Any | MYSQL cluster restart failing after initialization |
88627 | 2017-11-23 15:23 | 2017-12-18 16:20 | MySQL Cluster: Cluster (NDB) storage engine | Not a Bug (2293 days) | S2 | ndb-7.4.7 | CentOS (6.6) | Any | MySQl cluster is wiping a databasse data during initialization of one ndb node |
105199 | 2021-10-13 6:41 | 2021-10-19 7:49 | MySQL Cluster: Cluster (NDB) storage engine | Verified (892 days) | S2 | 7.5.22 | CentOS (7.8.2003) | x86 | ndbcluster: Tuple corruption detected, exiting |
90908 | 2018-05-17 9:16 | 2018-05-28 16:24 | MySQL Cluster: Cluster (NDB) storage engine | Can't repeat (2133 days) | S2 | ndb-7.5.9 | CentOS (7 64 bit) | x86 | Error: 2341 - Internal error, DBACC (Line: 1445) in ndbmtd |
111978 | 2023-08-04 14:22 | 2023-08-10 14:27 | MySQL Cluster: Replication | Can't repeat (232 days) | S1 | 8.0.30 | CentOS (CentOS Linux release 7.7.1908 (Core)) | x86 (Intel(R) Xeon(R) Gold 5220 CPU @ 2.20GHz) | Our PRD env mysql 8.0.30 group-replication cluster lost some data |
109262 | 2022-12-01 14:34 | 2022-12-10 2:15 | MySQL Cluster: Replication | Verified (479 days) | S2 | 8.0.30 | CentOS (centos 7.9.2009) | x86 (x86-64) | when communicationStack=mysql,then rebootClusterFromCompleteOutage will hang |
91100 | 2018-06-01 5:31 | 2018-06-29 11:30 | MySQL Cluster: Cluster (NDB) storage engine | Closed (2100 days) | S3 | mysql-5.6.22 ndb-7.3.8 | CentOS (Linux 3.10.0-514.el7.x86_64) | x86 | NDB node can not pass phase 5 after restart. Error:2303 |
91865 | 2018-08-02 8:17 | 2018-08-10 13:43 | MySQL Cluster: Cluster (NDB) storage engine | Not a Bug (2058 days) | S3 | 5.6.41 ndb-7.4.21 | CentOS (6.3) | x86 | mysqld crashes with signal 6 |
Showing 1-30 of 42 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |