MySQL Bugs: #41292: GCP stop errors exits both data nodes

Bug #41292	GCP stop errors exits both data nodes
Submitted:	8 Dec 2008 11:18	Modified:	25 Mar 12:06
Reporter:	Geert Vanderkelen
Status:	Duplicate
Category:	Server: Cluster	Severity:	S2 (Serious)
Version:	mysql-5.1.30-ndb-6.3.20	OS:	Any
Assigned to:	Geert Vanderkelen	Target Version:

Description:
While testing bug #28622 I ran once in some temporary errors with the infamous GCP stop..
Why I didn't open new bug for that, no idea :(
Here is how to reproduce it.

How to repeat:
Basically, test case of #28622:

Three tables, all having the same DDL:

CREATE TABLE `tab1` (
  `id` char(12) NOT NULL,
  `timestamp` timestamp NOT NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP,
  PRIMARY KEY  (`id`)
) ENGINE=ndbcluster DEFAULT CHARSET=ascii;

CREATE TABLE `tab1_newdata` (
  `id` char(12) NOT NULL,
  `timestamp` timestamp NOT NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP,
  PRIMARY KEY  (`id`)
) ENGINE=ndbcluster DEFAULT CHARSET=ascii;

CREATE TABLE `tab2` (
  `id` char(12) NOT NULL,
  `timestamp` timestamp NOT NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP,
  PRIMARY KEY  (`id`)
) ENGINE=ndbcluster DEFAULT CHARSET=ascii;

The small C application populating tables on bug #28622.
Then do the following concurrently:

shell_1> while true; do /data1/mysql/ndb-6.3.18/bin/mysql test -e "REPLACE INTO tab1
SELECT * FROM tab1_newdata"; done

shell_2> while true; do /data1/mysql/ndb-6.3.18/bin/mysql test -e "DELETE from tab2 where
timestamp<(CURDATE()-1)"; done

Eventually both nodes will get temporary error.

Verified using MySQL Cluster 6.3.18 and 6.3bzr (latest pull)

GCP Stop

Attachment: ndb_error_report_20081208110944.tar.bz2 (application/octet-stream, text), 86.64 KiB.

Might be a simple load problem. Error message GCP stop is a bit generic in this repect.

http://bugs.mysql.com/bug.php?id=37227