Bug #61913 Mysqld crashes with ndb_cluster_connection_pool=8
Submitted: 19 Jul 2011 19:19 Modified: 16 Sep 2011 9:27
Reporter: Johan Andersson Email Updates:
Status: No Feedback Impact on me:
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:7.1.14, 7.1.15 OS:Linux (kernel 2.6.35)
Assigned to: Assigned Account CPU Architecture:Any
Tags: ndb_cluster_connection_pool

[19 Jul 2011 19:19] Johan Andersson
110719 19:16:31 [Note] NDB: NodeID is 5, management server ''
110719 19:16:32 [Note] NDB[0]: NodeID: 5, all storage nodes connected
110719 19:16:32 [Note] NDB[1]: NodeID: 6, all storage nodes connected
110719 19:16:33 [Note] NDB[2]: NodeID: 7, all storage nodes connected
110719 19:16:34 [Note] NDB[3]: NodeID: 8, all storage nodes connected
110719 19:16:34 [Note] NDB[4]: NodeID: 9, all storage nodes connected
110719 19:16:35 [Note] NDB[5]: NodeID: 10, all storage nodes connected
110719 19:16:35 [Note] NDB[6]: NodeID: 11, all storage nodes connected
110719 19:16:36 [Note] NDB[7]: NodeID: 12, all storage nodes connected
110719 19:16:36 [Warning] NDB: server id set to zero - changes logged to bin log with server id zero will be logged with another server id by slave mysqlds
110719 19:16:36 [Note] Starting Cluster Binlog Thread

Status information:

Current dir: /storage/data/mysql/
Running threads: 0  Stack size: 262144
Current locks:

Key caches:
Buffer_size:       8384512
Block_size:           1024
Division_limit:        100
Age_limit:             300
blocks used:             0
not flushed:             0
w_requests:              0
writes:                  0
r_requests:              0
reads:                   0

handler status:
read_key:            0
read_next:           0
read_rnd             0
read_first:          0
write:               0
delete               0
update:              0

Table status:
Opened tables:          1
Open tables:            0
Open files:             0
Open streams:           0

Alarm status:
Active alarms:   0
Max used alarms: 0
Next alarm time: 0

Begin safemalloc memory dump:

End safemalloc memory dump.
110719 19:16:36 - mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 163859 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = (nil) thread_stack 0x40000
110719 19:16:36 [Note] Event Scheduler: Loaded 0 events
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.

Memory status:
Non-mmapped space allocated from system: 6504448
Number of free chunks:			 33
Number of fastbin blocks:		 0
Number of mmapped regions:		 43
Space in mmapped regions:		 226627584
Maximum total allocated space:		 0
Space available in freed fastbin blocks: 0
Total allocated space:			 6368704
Total free space:			 135744
Top-most, releasable space:		 131408
Estimated memory (with thread stack):    233132032

Events status:
LLA = Last Locked At  LUA = Last Unlocked At
WOC = Waiting On Condition  DL = Data Locked

Event scheduler status:

glibc-2.12  if it helps..

How to repeat:
start a mysqld with :

[16 Aug 2011 9:13] Geert Vanderkelen
Could not repeat with MySQL Cluster 7.1.15 and glibc 2.5.
[16 Aug 2011 9:27] Geert Vanderkelen
Which Linux Distro was used?
[16 Sep 2011 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".