Bug #9916 DbaccMain.cpp / DBACC (Line: 4876) / Pointer too large
Submitted: 14 Apr 2005 17:45 Modified: 14 Apr 2005 20:40
Reporter: Ted Schundler Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S1 (Critical)
Version:4.1.10 OS:FreeBSD (FreeBSD 5.4)
Assigned to: CPU Architecture:Any

[14 Apr 2005 17:45] Ted Schundler 
Description:
Seemingly randomly, ndbd nodes die due to the following error:

Type of error: error
Message: Pointer too large
Fault ID: 2306
Problem data: DbaccMain.cpp
Object of reference: DBACC (Line: 4876) 0x00000002
ProgramName: /usr/local/libexec/ndbd
ProcessID: 65240
TraceFile: /var/db/mysql-cluster/ndb_1_trace.log.18

I can mail the trace on request.
Sometimes it happens on just one node, and the cluster itself isn't affected. But most of the time, it seems to happen seconds later on the other node.

Setup:
HostA : ndbd + api (high use: > 30 queries / sec -- 42% select, 36% update, 13% lock/unlock tables, 2% replace, 1% insert)
HostB: ndbd + api (same usage as Host A
HostC: mgm + api (very low api usage)

NoOfReplicas= 2
DataDir= /var/db/mysql-cluster
IndexMemory= 150M
DataMemory= 240M
TransactionBufferMemory= 4M
MaxNoOfAttributes= 2048
MaxNoOfTables=550
MaxNoOfOrderedIndexes=480
MaxNoOfUniqueHashIndexes=360
MaxNoOfConcurrentTransactions=16384
MaxNoOfConcurrentOperations=65536
TransactionInactiveTimeout=10000

As a MyIASM database, it uses about 10MB for a bit over 100,000 rows across 57 tables.

How to repeat:
Setup exactly my database with the same load?
Unfortunately I didn't have a problem with this in any of my smaller tests with ndb, but rather only when trying to use it in production where it takes a reasonably heavy load.
[14 Apr 2005 20:40] Pekka Nousiainen 
Thank you for your bug report. This issue has already been fixed
in the latest released version of that product, which you can download at 
http://www.mysql.com/downloads/

Additional info:

Fixed in current version 4.1.11 (no previous bug report was filed).
Context: delete via ordered index on table where primary key is >32 bytes.