MySQL Bugs: #13965: Cluster: MaxNoOfAttributes set too low does not produce error message

Bug #13965	Cluster: MaxNoOfAttributes set too low does not produce error message
Submitted:	12 Oct 2005 16:05	Modified:	14 Feb 2006 8:25
Reporter:	Jonathan Miller	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S3 (Non-critical)
Version:	4.1, 5.0, 5.1	OS:	Linux (Linux)
Assigned to:	Jonas Oreland	CPU Architecture:	Any

Description:
I changed MaxNoOfAttributes: from 1500 to 32 and restarted the cluster. Listed here are the errors recieved:

Cluster Log:
2005-10-12 17:57:41 [MgmSrvr] INFO     -- Node 8: Start phase 3 completed (system restart)
2005-10-12 17:57:45 [MgmSrvr] INFO     -- Node 1: Node 5 Connected
2005-10-12 17:57:45 [MgmSrvr] ALERT    -- Node 6: Node 5 Disconnected
2005-10-12 17:57:45 [MgmSrvr] INFO     -- Node 6: Communication to Node 5 closed2005-10-12 17:57:45 [MgmSrvr] ALERT    -- Node 8: Node 5 Disconnected
2005-10-12 17:57:45 [MgmSrvr] INFO     -- Node 8: Communication to Node 5 closed2005-10-12 17:57:45 [MgmSrvr] ALERT    -- Node 9: Node 5 Disconnected
2005-10-12 17:57:45 [MgmSrvr] INFO     -- Node 9: Communication to Node 5 closed2005-10-12 17:57:45 [MgmSrvr] ALERT    -- Node 5: Forced node shutdown completed. Occured during startphase 4. Initiated by signal 0. Caused by error 2341: 'Internal program error (failed ndbrequire)(Internal error, programming error or missing error message, please report a bug). Temporary error
2005-10-12 17:57:46 [MgmSrvr] ALERT    -- Node 6: Node 8 Disconnected
2005-10-12 17:57:46 [MgmSrvr] INFO     -- Node 6: Possible bug in Dbdih::execBLOCK_COMMIT_ORD c_blockCommit = 1 c_blockCommitNo = 2 sig->failNo =
2005-10-12 17:57:46 [MgmSrvr] INFO     -- Node 6: Communication to Node 5 closed2005-10-12 17:57:46 [MgmSrvr] INFO     -- Node 6: Communication to Node 8 closed2005-10-12 17:57:46 [MgmSrvr] INFO     -- Node 1: Node 8 Connected
2005-10-12 17:57:46 [MgmSrvr] ALERT    -- Node 9: Node 8 Disconnected
2005-10-12 17:57:46 [MgmSrvr] INFO     -- Node 9: Possible bug in Dbdih::execBLOCK_COMMIT_ORD c_blockCommit = 1 c_blockCommitNo = 2 sig->failNo =
2005-10-12 17:57:46 [MgmSrvr] INFO     -- Node 9: Communication to Node 5 closed2005-10-12 17:57:46 [MgmSrvr] INFO     -- Node 9: Communication to Node 8 closed2005-10-12 17:57:46 [MgmSrvr] ALERT    -- Node 8: Forced node shutdown completed. Occured during startphase 4. Initiated by signal 0. Caused by error 2308: 'Another node failed during system restart, please investigate error(s) on other node(s)(Restart error). Temporary error, restart node'.
2005-10-12 17:57:47 [MgmSrvr] INFO     -- Node 1: Node 6 Connected
2005-10-12 17:57:47 [MgmSrvr] ALERT    -- Node 6: Forced node shutdown completed. Occured during startphase 4. Initiated by signal 0. Caused by error 2305: 'Arbitrator shutdown, please investigate error(s) on other node(s)(Arbitration error). Temporary error, restart node'.
2005-10-12 17:57:48 [MgmSrvr] INFO     -- Node 1: Node 9 Connected
2005-10-12 17:57:48 [MgmSrvr] ALERT    -- Node 9: Forced node shutdown completed. Occured during startphase 4. Initiated by signal 0. Caused by error 2305: 'Arbitrator shutdown, please investigate error(s) on other node(s)(Arbitration error). Temporary error, restart node'.

Node error logs:

Time: Wednesday 12 October 2005 - 17:56:35
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: Dbdict.cpp
Error object: DBDICT (Line: 2575) 0x0000000a
Program: /home/ndbdev/jmiller/builds/libexec/ndbd
Pid: 14590
Trace: /space/run/ndb_5_trace.log.1
Version: Version 5.1.2 (a_drop5p5)
***EOM***

Current byte-offset of file-pointer is: 1067

Time: Wednesday 12 October 2005 - 17:52:22
Status: Temporary error, restart node
Message: Arbitrator shutdown, please investigate error(s) on other node(s) (Arbitration error)
Error: 2305
Error data: Arbitrator decided to shutdown this node
Error object: QMGR (Line: 3813) 0x0000000a
Program: /home/ndbdev/jmiller/builds/libexec/ndbd
Pid: 14470
Trace: /space/run/ndb_8_trace.log.1
Version: Version 5.1.2 (a_drop5p5)

Time: Wednesday 12 October 2005 - 17:52:21
Status: Temporary error, restart node
Message: Another node failed during system restart, please investigate error(s) on other node(s) (Restart error)
Error: 2308
Error data: Unhandled node failure during restart
Error object: NDBCNTR (Line: 1437) 0x0000000a
Program: /home/ndbdev/jmiller/builds/libexec/ndbd
Pid: 4940
Trace: /space/run/ndb_6_trace.log.1
Version: Version 5.1.2 (a_drop5p5)

Time: Wednesday 12 October 2005 - 17:52:23
Status: Temporary error, restart node
Message: Arbitrator shutdown, please investigate error(s) on other node(s) (Arbitration error)
Error: 2305
Error data: Arbitrator decided to shutdown this node
Error object: QMGR (Line: 3813) 0x0000000a
Program: /home/ndbdev/jmiller/builds/libexec/ndbd
Pid: 4943
Trace: /space/run/ndb_9_trace.log.1
Version: Version 5.1.2 (a_drop5p5)
***EOM***

ndb_5_trace.log.1
--------------- Signal ----------------
r.bn: 250 "DBDICT", r.proc: 5, r.sigId: 957493 gsn: 255 "FSCLOSECONF" prio: 1
s.bn: 253 "NDBFS", s.proc: 5, s.sigId: 957491 length: 1 trace: 0 #sec: 0 fragInf: 0
 UserPointer: 0

ndb_8_trace.log.1
--------------- Signal ----------------
r.bn: 252 "QMGR", r.proc: 8, r.sigId: 1041230 gsn: 343 "PREP_FAILCONF" prio: 0
s.bn: 252 "QMGR", s.proc: 9, s.sigId: 1023616 length: 2 trace: 8 #sec: 0 fragInf: 0
 H'00000009 H'00000003

How to repeat:
see above

I was able to reproduce this using FC4 and a recent 5.0 clone

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/2176

pushed into 5.1.7

pushed into 5.0.19

I would like the comment changed to "Likely invalid change of configuration" when time allows.

Will move request to different bug report.

pushed into 4.1.19

Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html

Additional info:

Documented bugfix in 4.1.19, 5.0.19, and 5.1.7 changelogs. Closed.