MySQL Bugs: #46069: Data node crashes during normal operation at Dbacc::readTablePk

Bug #46069	Data node crashes during normal operation at Dbacc::readTablePk
Submitted:	9 Jul 2009 1:12	Modified:	10 Aug 2009 10:32
Reporter:	Mikiya Okuno	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S2 (Serious)
Version:	*	OS:	Any
Assigned to:	Jonas Oreland	CPU Architecture:	Any

Description:
The error log appears like below:

Time: XXXXXXXXXXX MASKED XXXXXXXXXXX
Status: Temporary error, restart node
Message: Internal program error (failed ndbrequire) (Internal error, programming error or missing error message, please report a bug)
Error: 2341
Error data: dbacc/DbaccMain.cpp
Error object: DBACC (Line: 3218) 0x00000008
Program: ndbd
Pid: XXXXXXXXXXX MASKED XXXXXXXXXXX
Trace: XXXXXXXXXXX MASKED XXXXXXXXXXX
Version: mysql-5.1.30 ndb-6.3.20-GA
***EOM***

How to repeat:
unknown. this happens suddenly.

Suggested fix:
n/a

proposed patch

Attachment: bug46069.patch (text/x-patch), 1.03 KiB.

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/80348

2961 Jonas Oreland	2009-08-07
      ndb - bug#46069
        Fix crash in ACC caused by assertion fire-ing due to TUX LOCK_REQ
          did not set OP_COMMIT_DELETE_CHECK during setup

DOCS:
Problem was when combining index-scan+delete with primary key delete
The index-scan delete failed set properly initialize a flag,
causing a rare assertion.

The missing initialization of the flag did how-ever not have any bad effect
(except the rare assertion :-)

pushed to 6.2.19, 6.3.26 and 7.0.7

Documented bugfix in the NDB 6.2.19, 6.3.26, and 7.0.7 changelogs as follows:

      When combining an index scan and a delete with a primary key delete, the
      index scan and delete failed to initialize a flag properly. This could in
      rare circumstances cause a data node to crash.