Repeatable Lock/Unlock Tables crash with NDBCLUSTER

From: <kal(at)nyc.rr.com>
Date: Tue Aug 14 2007 - 09:49:01 EDT

Hello,

I am assuming this bug pertains to MySQL cluster.

I am experiencing a repeatable crash with NDBCLUSTER tables.

MySQL version:

MySQL-client-community-5.0.45-0.rhel4.i386.rpm
MySQL-clustermanagement-community-5.0.45-0.rhel4.i386.rpm
MySQL-clusterstorage-community-5.0.45-0.rhel4.i386.rpm
MySQL-clustertools-community-5.0.45-0.rhel4.i386.rpm
MySQL-server-community-5.0.45-0.rhel4.i386.rpm

Create NDBCLUSTER table...

CREATE TABLE t_test_crash (

  test_id BIGINT NOT NULL AUTO_INCREMENT PRIMARY KEY,
  test_name VARCHAR(256) NOT NULL,
  test_id_2 BIGINT NOT NULL,

  updated_tm TIMESTAMP NOT NULL,
  created_tm TIMESTAMP NOT NULL,
  UNIQUE INDEX idx_test ( test_name, test_id_2 ),

  INDEX idx_test_2 ( test_id_2 ),
  INDEX idx_updated_tm ( updated_tm ),
  INDEX idx_created_tm ( created_tm )

)
AUTO_INCREMENT = 1
ENGINE = NDBCLUSTER
DEFAULT CHARACTER SET utf8
DEFAULT COLLATE utf8_bin;

Issue queries as such...

> LOCK TABLES t_test_crash WRITE;
> DELETE FROM t_test_crash WHERE test_id_2 = 1;
> INSERT INTO t_test_crash ( test_name, test_id_2, updated_tm,
created_tm ) VALUES ( "test", 1, now(), now() );
> UNLOCK TABLES;
Error log...

070814 9:33:03 - 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=536870912
read_buffer_size=10481664
max_used_connections=1
max_connections=16384
threads_connected=1
It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 458624 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0x8bd04d0
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=0x94f2cc0c, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x81c2007
0x8295ec4
0x8295fba
0x8288c68
0x81fcff2
0x81fd09c
0x81d2c41
0x81d9178
0x81df4f9
0x81e036f
0x81e0d67
0x81e17a0
0xc4d371
0xad4ffe
New value of fp=(nil) failed sanity check, terminating stack trace! 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 0x8c08b20 = UNLOCK TABLES
thd->thread_id=2
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

Number of processes running now: 0
070814 09:33:03 mysqld restarted
070814 9:33:07 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.0.45-community-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Edition (GPL)

I am able to avoid the crash by calling 'UNLOCK TABLES' after the DELETE, and then 'LOCK TABLES' again before the INSERT.

Has this been a known issue?

Regards,
Kal

-- 
MySQL Bugs Mailing List
For list archives: 
http://lists.mysql.com/bugs
To unsubscribe:    
http://lists.mysql.com/bugs?unsub=lists@pantek.com

Received on Tue Aug 14 09:44:17 2007