MySQL Bugs: #34061: Replication fails between 2 clusters with disk tables

Bug #34061	Replication fails between 2 clusters with disk tables
Submitted:	25 Jan 2008 15:56	Modified:	10 May 2008 21:53
Reporter:	Cyril SCETBON	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Cluster: Replication	Severity:	S2 (Serious)
Version:	5.1.22	OS:	Linux (debian etch)
Assigned to:		CPU Architecture:	Any

Description:
Using replication between 2 clusters with disk table and a lot of requests produces some errors :

Error in Write_rows event: error during
transaction execution on table spp.spp_disk01. Got error 839
'Illegal null attribute' from NDBCLUSTER

and

Error in Write_rows event: error during
transaction execution on table spp.spp_disk01. Can't find
record in 'spp_disk01'

It does not appear when we use mysql client to connect to the cluster but when we use ndb client. The difference is that we can't increase the load on the mysql client (limited cause it's single-threaded) whereas with ndb we can have multiple connections to the cluster.

How to repeat:
use a disk table and replicate it between 2 clusters :

CREATE TABLE `spp_disk01` (
  `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  `ise` varchar(54) NOT NULL,
  `vc01` varchar(400) NOT NULL DEFAULT '',
  `vc02` varchar(1200) NOT NULL DEFAULT '',
  `ch03` char(10) NOT NULL DEFAULT '',
  `vc04` varchar(11) NOT NULL DEFAULT '-1',
  `vc05` varchar(11) NOT NULL DEFAULT '-1',
  `ch06` char(10) NOT NULL DEFAULT '',
  `ch07` char(10) NOT NULL DEFAULT '',
  `ch08` char(1) NOT NULL DEFAULT '',
  `ch09` char(3) NOT NULL DEFAULT '',
  `ch10` char(10) NOT NULL DEFAULT '',
  `in11` int(11) NOT NULL DEFAULT '-1',
  `in12` int(11) NOT NULL DEFAULT '-1',
  `vc13` varchar(255) NOT NULL DEFAULT '',
  `vc14` varchar(255) NOT NULL DEFAULT '',
  `ts15` timestamp NOT NULL DEFAULT '0000-00-00 00:00:00',
  `ts16` timestamp NOT NULL DEFAULT '0000-00-00 00:00:00',
  `tx17` text CHARACTER SET utf8,
  `tx18` text CHARACTER SET utf8,
  `tx19` text CHARACTER SET utf8,
  `ts` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
  PRIMARY KEY (`id`),
  UNIQUE KEY `ise` (`ise`)
) /*!50100 TABLESPACE ts_1 STORAGE DISK */ ENGINE=ndbcluster DEFAULT CHARSET=latin1;

mix insert/update up to 470 write/s

Hi,

Is it possible to get snapshot data and example of queries that you run?

/Jonas

Cyril,

could you please provide data requested by Jonas?

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".