MySQL Bugs: #66982: NDBD suddenly shutdown when execute some SQL queries

Bug #66982	NDBD suddenly shutdown when execute some SQL queries
Submitted:	27 Sep 2012 7:52	Modified:	18 Feb 2013 21:36
Reporter:	Chun Chan	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S2 (Serious)
Version:	7.2.5	OS:	Linux (Red Hat Enterprise Linux Server release 6.2 (Santiago))
Assigned to:	Assigned Account	CPU Architecture:	Any

Description:
When i tried to execute some SQL queries, i found that all data nodes were shutdown suddenly. After checking the logs, we found that it was caused by internal program error shown as following.

ndb_3_error.log:

Time: Thursday 27 September 2012 - 09:48:06
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: DbspjMain.cpp
Error object: DBSPJ (Line: 888) 0x00000002
Program: ndbd
Pid: 2095
Version: mysql-5.5.20 ndb-7.2.5
Trace: /ummc/mysql/ndbdata/ndb_3_trace.log.1 [t1..t1]
***EOM***

How to repeat:
Unknown...

Hi Chun,

I will need more information to understand the issue better and/or possibly reproduce it locally. Can you provide the following, please?

- config files e.g config.ini, my.cnf
- log files and error report (use ndb_error_reporter)
- steps to reproduce the issue or hints like type of load on the cluster, any specific query or set of queries that should be running on the cluster etc.
- Did you set ndb_join_pushdown to 1? Can you try again after setting ndb_join_pushdown to 0? More details about the variables can be found at http://dev.mysql.com/doc/refman/5.5/en/mysql-cluster-system-variables.html#sysvar_ndb_join... .

Please include any additional information that might be helpful.

Thanks.

Hi Chun,

A similar internal bug was fixed in NDB-7.2.6, so I was wondering if you could try and reproduce this issue locally on a cluster (in lab/test environment) using similar data and traffic and then upgrade to the latest available cluster release and see if that fixes the problem.

Thanks.

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".