Bug #22547 Node crash is for max value of LongMessageBuffer
Submitted: 21 Sep 2006 13:17 Modified: 7 Dec 2006 4:12
Reporter: Serge Kozlov Email Updates:
Status: Closed Impact on me:
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S2 (Serious)
Version:5.1.12 (beta) OS:
Assigned to: Guangbao Ni CPU Architecture:Any

[21 Sep 2006 13:17] Serge Kozlov
Both ndbd node crashes if config has Max value for LongMessageBuffer (4294967039).

How to repeat:
1. Create a new config.ini with LongMessageBuffer=4294967039
2. Start cluster
3. Look at error and core files.

Suggested fix:
It seems that error message is correct (memory allocation failure), but why core files appear...
[21 Sep 2006 13:22] Serge Kozlov
Error/core files and config.ini

Attachment: bugLongMessageBuffer.Max.zip (application/x-zip-compressed, text), 1.49 KiB.

[7 Dec 2006 1:29] Guangbao Ni
I don't know why the comment and patch for bug#22547 can't see here. 
I paste them here.

# ChangeSet
#   2006/10/19 13:49:32+08:00 gni@dev3-127.(none)
#   BUG #22547 LongMessageBuffer too large causes ndbd to exit and gives
the exact paramter name in error log.
# storage/ndb/src/kernel/blocks/cmvmi/Cmvmi.cpp
#   2006/10/19 13:49:30+08:00 gni@dev3-127.(none) +2 -1
#   Add a parameter id parameter for setSize method. When allocating
memory error results in ndbd exit can gives exact parameter name in error log.
diff -Nru a/storage/ndb/src/kernel/blocks/cmvmi/Cmvmi.cpp
--- a/storage/ndb/src/kernel/blocks/cmvmi/Cmvmi.cpp     2006-10-19
13:55:00 +08:00
+++ b/storage/ndb/src/kernel/blocks/cmvmi/Cmvmi.cpp     2006-10-19
13:55:00 +08:00
@@ -62,7 +62,8 @@

   long_sig_buffer_size= long_sig_buffer_size / 256;
-  g_sectionSegmentPool.setSize(long_sig_buffer_size);
+  g_sectionSegmentPool.setSize(long_sig_buffer_size,
+                               false,true,true,CFG_DB_LONG_SIGNAL_BUFFER);

   // Add received signals
   addRecSignal(GSN_CONNECT_REP, &Cmvmi::execCONNECT_REP);
[7 Dec 2006 4:12] Jon Stephens
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 bug fix. More information about accessing the source trees is available at


Documented bugfix in 5.1.14 changelog. Thanks for the info.