MySQL Bugs: #18589: Error in write row event leads to failed data node on slave cluster (flexHammer)

Bug #18589	Error in write row event leads to failed data node on slave cluster (flexHammer)
Submitted:	28 Mar 2006 22:44	Modified:	21 Apr 2006 13:15
Reporter:	Jonathan Miller	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S2 (Serious)
Version:	5.1.9	OS:	Linux (Linux 32 Bit OS)
Assigned to:	Assigned Account	CPU Architecture:	Any

Description:
Slave Error Log:
060328 23:49:56 [ERROR] Slave: Error in Write_rows event: error during transaction execution on table hlr.matable, Error_code: 4031

../run/ndb_2_error.log
Current byte-offset of file-pointer is: 568
Time: Tuesday 28 Mars 2006 - 23:49:54
Status: Temporary error, restart node
Message: Internal program error (failed ndbrequire) (Internal error, programming error or missing error message, please report a bug)
Error: 2341
Error data: dbtup/DbtupExecQuery.cpp
Error object: DBTUP (Line: 1422) 0x0000000a
Program: /home/ndbdev/jmiller/builds/libexec/ndbd
Pid: 3275
Trace: /space/run/ndb_2_trace.log.1
Version: Version 5.1.9 (beta)
***EOM***

--------------- Signal ----------------
r.bn: 247 "DBLQH", r.proc: 2, r.sigId: 115738300 gsn: 98 "ACCKEYCONF" prio: 1
s.bn: 248 "DBACC", s.proc: 2, s.sigId: 115738297 length: 6 trace: 1 #sec: 0 fragInf: 0
 H'000007aa H'00000002 H'00000001 H'00002762 H'00000000 H'00000001
--------------- Signal ----------------
r.bn: 247 "DBLQH", r.proc: 2, r.sigId: 115738299 gsn: 330 "NEXT_SCANCONF" prio: 1
s.bn: 249 "DBTUP", s.proc: 2, s.sigId: 115738295 length: 1 trace: 4 #sec: 0 fragInf: 0
 H'00000000
--------------- Signal ----------------
r.bn: 245 "DBTC", r.proc: 2, r.sigId: 115738298 gsn: 164 "CONTINUEB" prio: 1
s.bn: 245 "DBTC", s.proc: 2, s.sigId: 115738294 length: 3 trace: 1 #sec: 0 fragInf: 0
 H'00000007 H'00001001 H'00019907
--------------- Signal ----------------
--------------- Signal ----------------
r.bn: 247 "DBLQH", r.proc: 2, r.sigId: 115738297 gsn: 342 "PACKED_SIGNAL" prio: 1
s.bn: 245 "DBTC", s.proc: 2, s.sigId: 115738294 length: 24 trace: 1 #sec: 0 fragInf: 0
Signal data: H'100006ef H'00000cb0 H'00700400 H'10000889 H'00000cb0 H'00700400 H'1000003f H'00000cb0 H'00700400 H'10000924 H'00000cb0 H'00700400 H'100007db H'00000cb0 H'00700400 H'10000e4d H'00000cb0 H'00700400 H'100001ff H'00000cb0 H'00700400 H'10000483 H'00000cb0 H'00700400
--------- Begin Packed Signals --------
--------------- Signal ----------------
r.bn: 247 "DBLQH", length: 3 "COMPLETE"
Signal data: H'100006ef H'00000cb0 H'00700400
--------------- Signal ----------------
r.bn: 247 "DBLQH", length: 3 "COMPLETE"
Signal data: H'10000889 H'00000cb0 H'00700400
--------------- Signal ----------------
r.bn: 247 "DBLQH", length: 3 "COMPLETE"
Signal data: H'1000003f H'00000cb0 H'00700400
--------------- Signal ----------------
r.bn: 247 "DBLQH", length: 3 "COMPLETE"
Signal data: H'10000924 H'00000cb0 H'00700400

Note: Cluster Stayed up and running on one data node.

How to repeat:
Not sure.

Found that I got same issues on master cluster today:

--------------- Signal ----------------
r.bn: 247 "DBLQH", r.proc: 4, r.sigId: 933155874 gsn: 98 "ACCKEYCONF" prio: 1
s.bn: 248 "DBACC", s.proc: 4, s.sigId: 933155865 length: 6 trace: 4 #sec: 0 fragInf: 0
 H'00000384 H'00000002 H'00000003 H'000011e2 H'00000000 H'00000001
--------------- Signal ----------------
r.bn: 249 "DBTUP", r.proc: 4, r.sigId: 933155873 gsn: 332 "NEXT_SCANREQ" prio: 1
s.bn: 247 "DBLQH", s.proc: 4, s.sigId: 933155861 length: 3 trace: 4 #sec: 0 fragInf: 0
 H'00000001 H'ffffffff H'00000002
--------------- Signal ----------------
r.bn: 247 "DBLQH", r.proc: 4, r.sigId: 933155872 gsn: 342 "PACKED_SIGNAL" prio: 1
s.bn: 247 "DBLQH", s.proc: 5, s.sigId: -1 length: 21 trace: 4 #sec: 0 fragInf: 0
Signal data: H'1000007c H'00004b6d H'00900a00 H'100005ac H'00004b6d H'00900a00 H'1000021d H'00004b6d H'00900a00 H'1000043b H'00004b6d H'00900a00 H'100005dd H'00004b6d H'00900a00 H'1000050c H'00004b6d H'00900a00 H'1000093c H'00004b6d H'00900a00
--------- Begin Packed Signals --------
Time: Wednesday 29 Mars 2006 - 02:31:40
Status: Temporary error, restart node
Message: Internal program error (failed ndbrequire) (Internal error, programming error or missing error message, please report a bug)
Error: 2341
Error data: dbtup/DbtupExecQuery.cpp
Error object: DBTUP (Line: 1422) 0x0000000a
Program: /home/ndbdev/jmiller/builds/libexec/ndbd
Pid: 31958
Trace: /space/run/ndb_4_trace.log.1
Version: Version 5.1.9 (beta)
***EOM***

This is a know bug in tup...has been around since I impl. "opt nr".
I get it everytime when running a ndbapi test program...

We believe this is a likely duplicate of

BUG#19245 Insert+Insert+rollback+rollback causes node failure