Bug #27193 Slave: Got error 4209 'Length parameter in equal/setValue is incorrect' from NDB
Submitted: 15 Mar 2007 23:43 Modified: 26 Mar 2007 10:37
Reporter: Johan Andersson Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Cluster: Replication Severity:S3 (Non-critical)
Version: 5.1.16-ndb-6.2.0-log OS:Any (*)
Assigned to: CPU Architecture:Any

[15 Mar 2007 23:43] Johan Andersson
Description:
mysql> select version();
+----------------------+
| version()            |
+----------------------+
| 5.1.16-ndb-6.2.0-log |
+----------------------+
1 row in set (0.04 sec)

mysql>

070315 18:31:00 [ERROR] Slave: Error in Write_rows event: row application failed, Error_code: 121
070315 18:31:00 [ERROR] Slave: Error in Write_rows event: error during transaction execution on table vlr.privateid, Error_code: 121
070315 18:31:00 [ERROR] Slave (additional info): Unknown error Error_code: 1105
070315 18:31:00 [Warning] Slave: Got error 4209 'Length parameter in equal/setValue is incorrect' from NDB Error_code: 1296
070315 18:31:00 [Warning] Slave: Got error 4209 'Length parameter in equal/setValue is incorrect' from NDB Error_code: 1296
070315 18:31:00 [Warning] Slave: Unknown error Error_code: 1105
070315 18:31:00 [Warning] Slave: Unknown error Error_code: 1105
070315 18:31:00 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'l118-bin.000001' position 4269116

How to repeat:
Two 1-node clusters.

Write a program that updates the master in a loop.
I update 8 bytes (bigint) using the NDBAPI in a loop.

This happens then immediately on the slave.

Guess it relates to
http://bugs.mysql.com/bug.php?id=25746
but it is closed...

B.R
johan

Suggested fix:
don't know...
[26 Mar 2007 10:37] Jonas Oreland
Analyzed and became #27378
Closing this as duplicate