Bug #64645 MySQL Cluster NDB 7.2.4 crash by error 2341

• Submitted: 14 Mar 2012 9:32
• Modified: 24 Apr 2012 17:31
• Reporter: zhang sl
• Status: No Feedback
• Category: MySQL Cluster: Cluster (NDB) storage engine
• Severity: S2 (Serious)
• Version: mysql-5.5.19 ndb-7.2.4
• OS: Linux (debian 6.0.2)
• CPU Architecture: Any
• Tags: MySQL Cluster NDB 7.2.4 crash by error 2341

[14 Mar 2012 9:32] zhang sl

Description:
Time: Wednesday 14 March 2012 - 15:18:25
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: DblqhMain.cpp
Error object: DBLQH (Line: 9764) 0x00000002
Program: ndbd
Pid: 8748
Version: mysql-5.5.19 ndb-7.2.4
Trace: /usr/local/mysql/data/ndb_2_trace.log.5 [t1..t1]

How to repeat:
i don't know

Suggested fix:
my configuration:

[ndbd default]
NoOfReplicas=2
DataMemory=512M
IndexMemory=100M
TimeBetweenLocalCheckpoints=2
[tcp default]
portnumber=2202

[ndb_mgmd]
# Management process options:
hostname=10.31.22.192
# Hostname or IP address of MGM node
datadir=/var/lib/mysql-cluster
# Directory for MGM node log files
[ndbd]
# Options for data node "A":
# (one [ndbd] section per data node)
hostname=10.31.22.196
# Hostname or IP address
datadir=/usr/local/mysql/data
NoOfFragmentLogFiles=64
# Directory for this data node's data files
[ndbd]
# Options for data node "B":
hostname=10.31.22.206
# Hostname or IP address
datadir=/usr/local/mysql/data
NoOfFragmentLogFiles=64
# Directory for this data node's data files
[mysqld]
# SQL node options:
hostname=10.31.22.181
# Hostname or IP address
# (additional mysqld connections can be
# specified for this node for various
# purposes such as running ndb_restore)
[mysqld]
hostname=10.31.22.196

[24 Mar 2012 17:31] Valeriy Kravchuk

Please, upload that /usr/local/mysql/data/ndb_2_trace.log.5. Please, check also if this crash ever happens with a newer version, 7.2.5.

[25 Apr 2012 1:00] Bugs System

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