Bug #48037 | ndbmtd cluster crash during insert of data (dbtup) | ||
---|---|---|---|
Submitted: | 14 Oct 2009 10:09 | Modified: | 20 Oct 2009 14:34 |
Reporter: | Johan Andersson | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S3 (Non-critical) |
Version: | mysql-5.1-telco-7.0 | OS: | Any |
Assigned to: | Jonas Oreland | CPU Architecture: | Any |
Tags: | cluster crash, dbtup |
[14 Oct 2009 10:09]
Johan Andersson
[19 Oct 2009 11:42]
Jonas Oreland
reproduced :-(
[20 Oct 2009 12:11]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/87458 3021 Jonas Oreland 2009-10-20 ndb - bug#48037 Fix various abort cases with indexes that could in worst case cause node-failure
[20 Oct 2009 12:33]
Jonas Oreland
pushed to 6.2.19, 6.3.28 and 7.0.9
[20 Oct 2009 14:34]
Jon Stephens
Documented bug fix in the NDB-6.2.19, 6.3.28, and 7.0.9 changelogs, as follows: In certain cases, performing very large inserts on NDB tables caused the memory allocations for ordered unique indexes to be exceeded. This could cause aborted transactions and possibly lead to data node failures. See also BUG#48113. Closed.
[28 Oct 2009 9:25]
Johan Andersson
Verified - can load data now without crash!