Bug #20334 LCP in parallel with TUPSCAN could cause node failure
Submitted: 8 Jun 2006 9:23 Modified: 14 Jun 2006 0:42
Reporter: Jonas Oreland Email Updates:
Status: Closed Impact on me:
Category:MySQL Cluster: Disk Data Severity:S3 (Non-critical)
Version:5.1 OS:
Assigned to: Jonas Oreland CPU Architecture:Any

[8 Jun 2006 9:23] Jonas Oreland
TUP handled LCP/TUP scan very poorly
Which could cause it to send NEXT_SCANCONF with incorrect scanPtr

User action needed: nothing really, could happen out of the blue
But running scans increased likelyhood

How to repeat:
[12 Jun 2006 11:40] Tomas Ulin
pushed to 5.1.12
[14 Jun 2006 0:42] 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.