Bug #10272 | "Index too large" error crashes ndbd | ||
---|---|---|---|
Submitted: | 29 Apr 2005 18:38 | Modified: | 1 May 2005 3:08 |
Reporter: | Ted Schundler | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S1 (Critical) |
Version: | 4.1.11 | OS: | FreeBSD (FreeBSD 5.4) |
Assigned to: | CPU Architecture: | Any |
[29 Apr 2005 18:38]
Ted Schundler
[1 May 2005 3:08]
Jorge del Conde
Hi, I can't reproduce this bug. Can you please send us a repeatable test-case that shows this behaviour ? Thanks
[11 May 2005 19:36]
Ted Schundler
No, like I mentioned, I can't repeat it. And they are very busy, so it's impossible to guess what could have triggered it. Like I mention, I can give you a trace file. But I need an E-Mail address to send it to as it's too big to attach.
[29 May 2007 12:26]
Kris Buytaert
Just ran into the same error on 4.1.12 (On Suse 8.2) This was the master node of a degraded cluster that crashed. The other node had been failing to restart on both an ndbd and ndbd --initial. Not reproducable , both nodes now are back up and running and I have no clue how I can get them back in the original error state. Current byte-offset of file-pointer is: 468 Date/Time: Tuesday 29 May 2007 - 11:34:23 Type of error: error Message: Index too large Fault ID: 2304 Problem data: DbdihMain.cpp Object of reference: DBDIH (Line: 11616) 0x0000000e ProgramName: ndbd ProcessID: 24787 TraceFile: /var/lib/mysql/mysql-cluster//ndb_3_trace.log.1 Version 4.1.12 ***EOM***
[29 May 2007 12:28]
Kris Buytaert
Error and Tracefile
Attachment: index_too_large.tar.gz (application/x-gzip, text), 47.34 KiB.