MySQL Bugs: #25468: Nf during LCP can lead to subsequent Nf

Bug #25468	Nf during LCP can lead to subsequent Nf
Submitted:	8 Jan 2007 17:36	Modified:	25 Jan 2007 5:01
Reporter:	Jonas Oreland	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S3 (Non-critical)
Version:		OS:
Assigned to:	Jonas Oreland	CPU Architecture:	Any

Description:
NF during LCP when only some nodes have received LCP_FRAG_REP from dying node
will lead to NF then node is restarted.

Those nodes that did/didnt receive last message (depedning on what master did)
  will fail.

How to repeat:
error inserts

Suggested fix:

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/17808

ChangeSet@1.2083, 2007-01-09 21:15:19+01:00, jonas@perch.ndb.mysql.com +4 -0
  ndb - bug#25468 
    handle partially transfered LCP_FRAG_REP after node failure
    (mysql-5.1-wl2325-5.0)

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/17881

ChangeSet@1.2362, 2007-01-10 20:50:19+01:00, jonas@perch.ndb.mysql.com +4 -0
  ndb - bug#25468
    handle partially transfered LCP_FRAG_REP after node failure
    recommit to 51-work

pushed to 5.1-ndb
wont be fixed in 5.0 and 4.1

pushed to 5.1.15

Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release.

If necessary, you can access the source repository and build the latest available version, including the bug fix. More information about accessing the source trees is available at

    http://dev.mysql.com/doc/en/installing-source.html

Documented bugfix in 5.1.15 changelog.