Bug #30037 Error in Delete_rows event; Error_code: 126
Submitted: 25 Jul 2007 13:12 Modified: 17 Mar 2008 15:07
Reporter: Erik Hoekstra Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Cluster: Replication Severity:S2 (Serious)
Version:5.1.20 OS:Linux (RedHat)
Assigned to: CPU Architecture:Any
Tags: delete, Delete_rows event, Error_code 126, replication

[25 Jul 2007 13:12] Erik Hoekstra
Description:
When deleting row's on a master from a table with, besides a primary key, an index. The slaves will crash the (in my case MyISAM) table, stop the master thread io and will comeup with this error in the log files;

 [ERROR] Slave SQL: Error in Delete_rows event: row application failed, Error_code: 126
 [ERROR] Slave SQL: Error in Delete_rows event: error during transaction execution on table db.t2, Error_code: 126

Useing 5.1.20 on a mysql-cluster setup with a replication from 2 api's to 2 individual slave's
    
    NDB.1        NDB.2
    API.1        API.2
    Slave.1      Slave.2

How to repeat:
On one of the masters (API.1, API.2)
CREATE TABLE `t2` (
  `id` mediumint(8) unsigned NOT NULL DEFAULT '0',
  `acc` varchar(8) CHARACTER SET utf8 COLLATE utf8_unicode_ci NOT NULL DEFAULT '',
  `n_id` enum('1','2') NOT NULL DEFAULT '1',
  `st` enum('1','2','3') CHARACTER SET utf8 COLLATE utf8_unicode_ci NOT NULL DEFAULT '2',
  PRIMARY KEY (`id`),
  KEY `acc` (`acc`)
) ENGINE = NDBCLUSTER;

INSERT INTO t2 VALUES (NULL, 'String', '2', '3');
... e.g. 1000x times?

DELETE FROM t2 WHERE xx.. ;

Suggested fix:
I tried to alter the table in different way's to locate the problem. After dropping the index the problem was gone.
[17 Feb 2008 15:07] Valeriy Kravchuk
Thank you for a problem report. Please, try to repeat with a newer version, 5.1.23-rc, and inform about the results.
[18 Mar 2008 0:02] Bugs System
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".