Bug #19768 Small cluster replication stress testing caused MySQLD signal 11
Submitted: 12 May 2006 13:14 Modified: 15 Jun 2006 10:29
Reporter: Jonathan Miller Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Cluster: Replication Severity:S1 (Critical)
Version:5.1.11 OS:Linux (Linux 32 Bit OS)
Assigned to: Tomas Ulin CPU Architecture:Any

[12 May 2006 13:14] Jonathan Miller
Description:
Version: '5.1.11-beta-log'  socket: '/tmp/mysql3307.sock'  port: 3307  Source distribution
out of order bucket: 1 gci: 965 m_latestGCI: 961
out of order bucket: 1 gci: 965 m_latestGCI: 961
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.

key_buffer_size=8388600
read_buffer_size=131072
max_used_connections=5
max_connections=100
threads_connected=4
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 225791 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0x9158b60
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...
Cannot determine thread, fp=0xb7ea9854, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x81dbfd2
0xf36420
0x83a8d5a
0x83a9f1c
0x83a8d5a
0x83bf39c
0x83bf56e
0x83bb59a
0x83c2370
0x83be2db
0x82d7d66
0x82d8673
0x82cff7b
0x82af4c2
0x82c5d8c
0x82d63cd
0x82da8e4
0x702b80
0x65a9ce

 resolve_stack_dump -s /tmp/mysqld.sym -n mysqld.stack
0x81dbfd2 handle_segfault + 438
0xf36420 (?)
0x83a8d5a _ZN3Ndb14releaseRecAttrEP10NdbRecAttr + 30
0x83a9f1c _ZN10NdbRecAttr7releaseEv + 54
0x83a8d5a _ZN3Ndb14releaseRecAttrEP10NdbRecAttr + 30
0x83bf39c _ZN21NdbEventOperationImpl4stopEv + 78
0x83bf56e _ZN21NdbEventOperationImplD1Ev + 40
0x83bb59a _ZN17NdbEventOperationD1Ev + 58
0x83c2370 _ZN14NdbEventBuffer20createEventOperationEPKcR8NdbError + 154
0x83be2db _ZN3Ndb20createEventOperationEPKc + 47
0x82d7d66 _Z27ndbcluster_create_event_opsP19st_ndbcluster_sharePKN13NdbDictionary5TableEPKc + 7020x82d8673 _Z30ndbcluster_create_binlog_setupP3NdbPKcjS2_S2_c + 973
0x82cff7b _ZN13ha_ndbcluster6createEPKcP8st_tableP24st_ha_create_information + 273
0x82af4c2 _Z27ha_create_table_from_engineP3THDPKcS2_ + 610
0x82c5d8c _Z28ndb_create_table_from_engineP3THDPKcS2_ + 104
0x82d63cd _Z37ndb_binlog_thread_handle_schema_eventP3THDP3NdbP17NdbEventOperationP4ListI14Cluster_schemaES8_P11st_mem_root + 383
0x82da8e4 ndb_binlog_thread_func + 2168
0x702b80 (?)
0x65a9ce (?)

How to repeat:
Master Cluster:
host 1 ndb_mgm, ndbd
host 2 ndbd
host 3 mysqld, mysqld
host 4 mysqld, mysqld
Slave Cluster:
host 1 ndb_mgm, ndbd, MySQLD
host 2 ndbd
Tests:
host 1 cid_ndb_dd.pl
host 3 TPC-B (8) total, 4 against each mysqld. Second MySQLD is the one that crashed.
[12 May 2006 13:21] Jonathan Miller
[ndbdev@ndb09 var]$ cat /etc/my.cnf
[manager]
default-mysqld-path = /home/ndbdev/jmiller/builds/libexec/mysqld
socket=/tmp/manager.sock
pid-file=/tmp/manager.pid
monitoring-interval = 50
port = 1999

[mysqld]
server-id=2
log-bin    = /space/var/ndb0901binlog
log-error  = /space/var/err.ndb0901.err
socket     = /tmp/mysql.sock
port       = 3306
pid-file   = /space/var/ndb0901.pid
datadir    = /space/var/
language   = /home/ndbdev/jmiller/builds/share/mysql/english/
ndbcluster                      # run NDB engine
ndb-connectstring=ndb08:14000  # location of MGM node

[mysqld2]
server-id=3
log-bin    = /space/var1/ndb0902binlog
log-error  = /space/var1/ndb0902.err
socket     = /tmp/mysql3307.sock
port       = 3307
pid-file   = /space/var1/ndb0902.pid
datadir    = /space/var1/
language   = /home/ndbdev/jmiller/builds/share/mysql/english/
ndbcluster                      # run NDB engine
ndb-connectstring=ndb08:14000  # location of MGM node
[14 Jun 2006 10:04] Tomas Ulin
pushed to 5.1.12
[15 Jun 2006 10:29] 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 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 5.1.12 changelog. Changed category to Cluster Replication. Closed.