Bug #42138 NDB crash -- failed handling of GCP_SAVEREQ
Submitted: 15 Jan 2009 18:04 Modified: 27 May 2009 16:50
Reporter: John David Duncan Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:mysql-5.1-telco-6.3 OS:Linux
Assigned to: Jon Stephens CPU Architecture:Any
Tags: 6.3.19

[15 Jan 2009 18:04] John David Duncan 
Description:
Crash in a 14-node cluster with ~ 1000 GB of data.  "Shutting down node due to failed handling of GCP_SAVEREQ Error object: DBLQH (Line: 19551) 0x0000000a ".

How to repeat:
unknown.
[15 Jan 2009 18:04] John David Duncan 
error logs from data nodes

Attachment: ndb_error_logs.tar.gz (application/x-gzip, text), 2.23 KiB.
[15 Jan 2009 18:11] John David Duncan 
configuration file

Attachment: cluster.ini (, text), 4.99 KiB.
[15 Jan 2009 19:09] Bernd Ocklin 
Hi, 

can you create a full error report containing all trace files, config, etc. by using the ndb_error_reporter command?

Thanks,

Bernd
[15 Jan 2009 22:47] John David Duncan 
I have uploaded ndb_error_reporter output to ftp.mysql.com/pub/mysql/upload -- the file name is ndb-error-bug-42138.tar.bz2
[27 May 2009 16:50] Jon Stephens 
Expected behaviour. E.g., description of DataMemory warns that this amount of physical memory must be free on the machine at all time for ndbd/ndbmtd to use.