Bug #31146 Killed node because GCP stop was detected

• Submitted: 22 Sep 2007 14:18
• Modified: 21 Jul 2008 13:46
• Reporter: Michael Neubert
• Status: Duplicate
• Category: MySQL Cluster: Cluster (NDB) storage engine
• Severity: S1 (Critical)
• Version: mysql-5.1.22 ndb-6.2.6-beta R1.2639
• OS: Any
• CPU Architecture: Any
• Tags: GCP

[22 Sep 2007 14:18] Michael Neubert

Description:
When using mysql-5.1.22 ndb-6.2.6-beta R1.2639 (and disk data tables) under high load data nodes crash with the following error:

Status: Temporary error, restart node
Message: System error, node killed during node restart by other node (Internal error, programming err or or missing error message, please report a bug)
Error: 2303
Error data: Node 2 killed this node because GCP stop was detected
Error object: NDBCNTR (Line: 235) 0x0000000a
Program: /usr/local/mysql/libexec/ndbd
Pid: 21885
Trace: /var/lib/mysql-cluster/ndb_2_trace.log.3
Version: mysql-5.1.22 ndb-6.2.6-beta
***EOM***  

The new GCP implementation / fixes introduced within the last 3 weeks before this release seem to be buggy.

How to repeat:
for example:
- add a new index to a big table (~ 4 GB data, 10 mio. rows)
- restore a big backup with ndb_restore

Suggested fix:
downgrade to mysql-5.1.22 ndb-6.2.5-beta R1.2584 until a fix is available

[6 Nov 2007 10:17] Tomas Ulin

duplicate 31276,

fixed in CGE 6.2.7

[21 Jul 2008 13:46] Michael Neubert

Hi,

the Bug-Report can be closed.

The problem was solved (as mentionned) in 

http://bugs.mysql.com/bug.php?id=31276

Best wishes
Michael