Bug #15908 NF of starting node during NR, when scan is complete on primary yields error
Submitted: 21 Dec 2005 15:27 Modified: 20 Jan 2006 15:49
Reporter: Jonas Oreland Email Updates:
Status: Closed Impact on me:
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:4.1,5.0,5.1 OS:
Assigned to: Jonas Oreland CPU Architecture:Any

[21 Dec 2005 15:27] Jonas Oreland
When scan is completed, but lqhkeyreq is outstanding on primary replica and starting node dies, scan will not be closed leading to error handling of failed node not completing

How to repeat:

Suggested fix:
[21 Dec 2005 15:29] 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:

[13 Jan 2006 9:51] Jonas Oreland
pushed into 5.0.19
[13 Jan 2006 11:59] Jonas Oreland
Pushed into 4.1.17 & 5.1.6
[20 Jan 2006 15:49] 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 changelogs for 4.1.17, 5.0.19, 5.1.6. Closed.