Bug #34534 ndbd nodes crash in SUMA subscribers after mysqld node shutdown
Submitted: 14 Feb 2008 5:42 Modified: 19 Jun 2009 12:16
Reporter: Sean Pringle Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S2 (Serious)
Version:mysql-5.1 OS:Any
Assigned to: Assigned Account CPU Architecture:Any
Tags: 5.1.22-rc

[14 Feb 2008 5:42] Sean Pringle
Description:
3 of 4 ndbd nodes crashed after a mysqld node shutdown:

Time: Thursday 31 January 2008 - 02:58:23
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: suma/Suma.cpp
Error object: SUMA (Line: 3168) 0x0000000a
Program: /usr/local/mysql/bin/ndbd
Pid: 3995
Trace: /s0/mysql-cluster/ndb_5_trace.log.1
Version: Version 5.1.22 (rc)
***EOM***

SUMA    003113 003131 003142 003173 003177 003189 003168

Suma::Table::checkRelease() manual abort with suma.suma_ndbrequire(false);

4th ndbd node then bailed out:

Time: Thursday 31 January 2008 - 02:58:24
Status: Temporary error, restart node
Message: Node lost connection to other nodes and can not form a unpartitioned cluster, please investigate if there are error(s) on other node(s) (Arbitration error)
Error: 2305
Error data: Arbitrator decided to shutdown this node
Error object: QMGR (Line: 4897) 0x0000000a
Program: /usr/local/mysql/bin/ndbd
Pid: 4144
Trace: /s0/mysql-cluster/ndb_2_trace.log.1
Version: Version 5.1.22 (rc)
***EOM***

QMGR    004278 004285 004306 004336 004352 004365 004428 004884 
        004886 004897

How to repeat:
n/a
[19 May 2009 12:16] Jonathan Miller
Are you still hitting this?
[19 Jun 2009 23: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".