MySQL Bugs: #21984: NDBD Error 2303 failed handling of GCP

Bug #21984	NDBD Error 2303 failed handling of GCP_SAVEREQ
Submitted:	4 Sep 2006 1:11	Modified:	2 Apr 2007 11:40
Reporter:	Adam Dixon (Candidate Quality Contributor)	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S3 (Non-critical)
Version:	5.0.21, 5.1.14-ndb-6.1.0-telco	OS:	Linux (RHEL4)
Assigned to:		CPU Architecture:	Any
Tags:	qc

Description:
Node crash with error 2303, the only thing I can put this event down to is disk load, which may lead this bug to be common with other already open bugs. http://bugs.mysql.com/bug.php?id=19706

The only thing I can put this to, is the fact that /etc/cron.daily started running 9 minutes prior to the node shutdown

Sep  2 04:00:01 c1s2 crond[4659]: (root) CMD (   cd /data/bin/; nice perl rsync_ctrl.pl )
Sep  2 04:01:01 c1s2 crond[4728]: (root) CMD (run-parts /etc/cron.hourly)
Sep  2 04:02:01 c1s2 crond[4730]: (root) CMD (run-parts /etc/cron.daily)
Sep  2 04:02:20 c1s2 anacron[5126]: Updated timestamp for job `cron.daily' to 2006-09-02

Possibly related to Bug 19706 but is has different error messages, so it may well be a failure in another segment of code. 

How to repeat:
More than likely disk contention related. Occured at same time as a few disk related cron jobs (backup/slocate etc).

See attached logs for details.

ndb_12_error.log

Attachment: ndb_12_error.log (text/x-log), 507 bytes.

ndb_12_out.log

Attachment: ndb_12_out.log (text/x-log), 12.47 KiB.

ndb_12_trace.log.2

Attachment: ndb_12_trace.log.2.gz (application/x-gzip, text), 52.75 KiB.

This looks very much like http://bugs.mysql.com/bug.php?id=20904
  and I just recently pushed a bug fix for that into 5.0.25

Could you possibly apply patch for that fix and try?
the bug fix is only removing "false" (and some printouts) 
  from a "if (false &&" statement

/Jonas

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

Duplicate of bug #20904.