Bug #47020 MySQL Cluster 7.0.5 datas nodes crash
Submitted: 31 Aug 2009 14:35 Modified: 2 Sep 2009 18:50
Reporter: Davy NESTOR Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S1 (Critical)
Version:7.0.5 OS:Linux
Assigned to: Assigned Account CPU Architecture:Any
Tags: 2341, datas crash, failed ndbrequire

[31 Aug 2009 14:35] Davy NESTOR
Description:
Hello,

I had my cluster running for a long time since I had to modify the transactiondeadlockdetectiontimeout value because of a recurrent error during some transaction.

lock wait timeout exceeded

I replaced the defaut value by 3000

After my modification and restart of the whole cluster, the system started to crash after just a couple of minutes.

I thought it was my modification, but after deleting this value, the cluster continued to crash.

In the datas nodes logs, there I have an error:

Internal program error (failed ndbrequire) (Internal error, programming error or missing error message, please report a bug)
#2341

I restarted the datas nodes with --initial option and  restore from a backup, but I don't know if this error can happen again.

How to repeat:
modify the transactiondeadlockdetectiontimeout value by 3000.

the cluster started to crash.
[31 Aug 2009 14:39] Davy NESTOR
manager configuration file

Attachment: config.ini (application/octet-stream, text), 2.51 KiB.

[31 Aug 2009 14:51] Davy NESTOR
Time: Monday 31 August 2009 - 14:54:49
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: dbtux/DbtuxCmp.cpp
Error object: DBTUX (Line: 138) 0x0000000a
Program: ndbd
Pid: 1152
Trace: /usr/local/mysql/data/ndb_3_trace.log.14
Version: mysql-5.1.32 ndb-7.0.5-beta
[2 Sep 2009 18:50] Jonas Oreland
duplicate of http://bugs.mysql.com/bug.php?id=45053
which was fixed in 7.0.7