Bug #19929 Uncommitted row could get skipped in opt. nr. making primary/backup inconsisten
Submitted: 19 May 2006 7:27 Modified: 14 Jun 2006 0:26
Reporter: Jonas Oreland Email Updates:
Status: Closed Impact on me:
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:5.1.5 -> OS:
Assigned to: Jonas Oreland CPU Architecture:Any

[19 May 2006 7:27] Jonas Oreland
When opt. nr found a record with gci < scanGCI
 it did not care if it was currently locked...

This meant that it could be skipped.

Meaning that starting node coudl miss transactions...
Causing pain and misery

How to repeat:

Suggested fix:
[19 May 2006 7:41] Bugs System
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:

[12 Jun 2006 11:39] Tomas Ulin
pushed to 5.1.12
[14 Jun 2006 0:26] Jon Stephens
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 bugfix, yourself. More information 
about accessing the source trees is available at

Additional info:

Documented bugfix in 5.1.12 changelog. Closed.