| « Show Previous 30 Entries | Showing 31-60 of 375 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 51996 | 2010-03-12 13:56 | 2011-02-16 23:44 | MySQL Cluster: Replication | Closed (4893 days) | S3 | mysql-5.1-telco-6.3 | Any | Any | rpl_geometry fails in mysql-5.1-telco-6.3 |
| 19247 | 2006-04-21 8:13 | 2006-04-28 9:19 | MySQL Cluster: Replication | Closed (6565 days) | S3 | Any | Huge memleak in replication of blobs | ||
| 20683 | 2006-06-25 9:47 | 2006-07-04 13:50 | MySQL Cluster: Replication | Closed (6498 days) | S3 | Any | Unhandled resource shortage in SUB_STOP_REQ causes node failure | ||
| 21563 | 2006-08-10 10:17 | 2007-09-17 11:55 | MySQL Cluster: Replication | Not a Bug (6058 days) | S3 | 5.1 | Any | Any | apply_status table is not recreated when binlog-format=statement |
| 21806 | 2006-08-24 8:44 | 2006-12-28 14:24 | MySQL Cluster: Replication | Closed (6321 days) | S3 | Any | Incorrect handling of cluster restart in binlog | ||
| 22802 | 2006-09-28 20:36 | 2006-11-08 9:23 | MySQL Cluster: Replication | Can't repeat (6371 days) | S3 | 5.1.2-a probaly 5.1 aswell | Any | Replication fails to retry failed commits making slave silently corrupt | |
| 25387 | 2007-01-03 14:15 | 2007-01-25 7:48 | MySQL Cluster: Replication | Closed (6293 days) | S3 | 5.1 | Any | mysqld assertion when starting with partial cluster and shutting down with full | |
| 25755 | 2007-01-22 16:14 | 2007-01-25 7:58 | MySQL Cluster: Replication | Closed (6293 days) | S3 | Any | Error in replication setup can lead to subsequent node failures | ||
| 27005 | 2007-03-09 15:29 | 2007-03-23 10:55 | MySQL Cluster: Replication | Closed (6236 days) | S3 | Any | Node failure + API failure can crash SUMA resend | ||
| 27651 | 2007-04-04 13:54 | 2007-04-17 11:44 | MySQL Cluster: Replication | Closed (6211 days) | S3 | 5.0-wl2325-5.0, 5.1* | Any | Any | Very high load can cause event api to get out of sync, "out of order buckets" |
| 27728 | 2007-04-10 7:17 | 2007-04-17 11:47 | MySQL Cluster: Replication | Closed (6211 days) | S3 | 5.1-wl2325-5.0, 5.1* | Any | Any | Partially connected API's can cause problem for SUMA |
| 31701 | 2007-10-18 20:11 | 2007-11-06 9:33 | MySQL Cluster: Replication | Closed (6008 days) | S3 | * | Any | Any | Node failure with repl. wo/ load, can lead to endless out of order buckets |
| 36123 | 2008-04-16 9:41 | 2008-05-09 19:17 | MySQL Cluster: Replication | Closed (5823 days) | S1 | 5.1 | Any | Any | Selecting from mysql.ndb_apply_status leads to failure |
| 38768 | 2008-08-13 12:24 | 2011-02-16 23:43 | MySQL Cluster: Replication | Closed (5674 days) | S3 | 6.3, 6.4 | Any | Any | Out of order buckets after parallel node restart |
| 17929 | 2006-03-05 10:50 | 2006-10-11 10:33 | MySQL Cluster: Disk Data | Closed (6399 days) | S3 | 5.1 | Any | DD: "delete from" is run in memory order | |
| 20334 | 2006-06-08 9:23 | 2006-06-14 0:42 | MySQL Cluster: Disk Data | Closed (6518 days) | S3 | 5.1 | Any | LCP in parallel with TUPSCAN could cause node failure | |
| 21710 | 2006-08-18 5:53 | 2006-09-01 16:24 | MySQL Cluster: Disk Data | Closed (6439 days) | S3 | 5.1 | Any | ndb_dd_dump indicates bug in drop file during lcp | |
| 21981 | 2006-09-03 9:31 | 2006-09-06 12:16 | MySQL Cluster: Disk Data | Closed (6434 days) | S3 | Any | ndbd crashes during CREATE LOGFILE GROUP if compiled with gcc4 (on some platform | ||
| 24331 | 2006-11-15 9:37 | 2006-12-07 4:57 | MySQL Cluster: Disk Data | Closed (6342 days) | S3 | Any | Any | Uninitialized record in LCP scan for diskdata | |
| 24917 | 2006-12-08 16:20 | 2006-12-28 14:08 | MySQL Cluster: Disk Data | Closed (6321 days) | S3 | 5.1 | Any | Makeing node restart with "newly" dropped disk table can cause failure during re | |
| 25636 | 2007-01-15 19:59 | 2007-01-25 7:37 | MySQL Cluster: Disk Data | Closed (6293 days) | S3 | 5.1 | Any | Node restart after 3 LCP's can cause incorrect UNDO to be run | |
| 26514 | 2007-02-21 3:43 | 2007-03-09 1:55 | MySQL Cluster: Disk Data | Closed (6250 days) | S3 | 5.1 | Any | Invalid memory access could occur during DD usage | |
| 27102 | 2007-03-13 19:58 | 2007-03-23 10:52 | MySQL Cluster: Disk Data | Closed (6236 days) | S3 | 5.1 | Any | Node can crash during flush of undo during restart with filesystem error | |
| 27462 | 2007-03-27 8:17 | 2007-09-30 19:05 | MySQL Cluster: Disk Data | Closed (6045 days) | S3 | 5.1 | Any | Any | Incorrect page bits after restart |
| 27757 | 2007-04-11 14:54 | 2007-04-17 11:16 | MySQL Cluster: Disk Data | Closed (6211 days) | S3 | 5.1 | Any | Any | Tup scan cant see own records |
| 27776 | 2007-04-12 4:56 | 2021-05-02 20:45 | MySQL Cluster: Disk Data | Verified | S3 | mysql-5.1 | Any | Any | Disk scan cant see uncommitted inserts by own transaction |
| 27882 | 2007-04-17 14:48 | 2007-10-26 6:01 | MySQL Cluster: Disk Data | Closed (6019 days) | S3 | 5.1 | Any | Any | Create TS with partial cluster followed by SR gives startup error |
| 28161 | 2007-04-30 9:29 | 2007-05-05 6:34 | MySQL Cluster: Disk Data | Closed (6193 days) | S3 | 5.1 | Any | Any | Detached triggers + DD and only MM update could cause node failure |
| 31229 | 2007-09-27 10:59 | 2007-12-15 9:33 | MySQL Cluster: Disk Data | Closed (5969 days) | S3 | 5.1 | Any | Any | Drop/truncate dd table can lead to node failure |
| 40921 | 2008-11-21 10:39 | 2011-02-16 23:43 | MySQL Cluster: Disk Data | Closed (5627 days) | S3 | Any | Any | Incorrectly handle resource shortage during create/drop DD object |
| « Show Previous 30 Entries | Showing 31-60 of 375 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
