Bug #24542 ndb_alter_table crashes in handle_trailing_share

• Submitted: 23 Nov 2006 12:41
• Modified: 24 Nov 2006 12:25
• Reporter: Mats Kindahl
• Status: Can't repeat
• Category: MySQL Cluster: Cluster (NDB) storage engine
• Severity: S1 (Critical)
• Version: 5.1.13 bk
• CPU Architecture: Any

[23 Nov 2006 12:41] Mats Kindahl

Description:
Ndb_alter_table test fails with an assertion.

mysqld: ha_ndbcluster.cc:7250: int handle_trailing_share(NDB_SHARE*): Assertion `(0)' failed.
mysqld got signal 6;
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=1048576
read_buffer_size=131072
max_used_connections=4
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 = 39423 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0xb3df9b8
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=0xb1d5e164, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x82c8d96
0x5227a2
0x568149
0x55fdb1
0x846f4d1
0x846f5c3
0x84651eb
0x84a6da0
0x84b15d7
Stack trace seems successful - bottom reached
Please read http://dev.mysql.com/doc/mysql/en/using-stack-trace.html and follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do 
resolve it
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0xb40b9c8 = alter table t2 add c int
thd->thread_id=5
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.
Writing a core file

How to repeat:
No idea.

[24 Nov 2006 12:25] Valeriy Kravchuk

Thank you for a problem report. Sorry, but I was not able to repeat the failure with current 5.1.14-BK on Linux:

openxs@suse:~/work/mysql-5.1/mysql-test> ./mysql-test-run.pl --mysqld=--binlog-
format=mixed --do-test=ndb_alter_table
Logging: ./mysql-test-run.pl --mysqld=--binlog-format=mixed --do-test=ndb_alter_
table
MySQL Version 5.1.14
mysql-test-run: WARNING: Could not parse variable list line : ndb-report-thresh-
binlog-epoch-slip3

mysql-test-run: WARNING: Could not parse variable list line : ndb-report-thresh-
binlog-mem-usage10

Using binlog format 'mixed'
Using ndbcluster when necessary, mysqld supports it
Setting mysqld to support SSL connections
Binaries are debug compiled
Killing Possible Leftover Processes
Removing Stale Files
Installing Master Database
Installing Master Database
Installing Master Cluster
=======================================================
Starting Tests in the 'main' suite

TEST                           RESULT         TIME (ms)
-------------------------------------------------------

ndb_alter_table                [ pass ]          48104
ndb_alter_table2               [ pass ]           5929
ndb_alter_table3               [ pass ]           7003
-------------------------------------------------------
Stopping All Servers
All 3 tests were successful.
The servers were restarted 1 times
Spent 61.036 seconds actually executing testcases