Bug #18414 Timeout in ABORT handling with more that 32 ops can yield NF
Submitted: 22 Mar 2006 9:47 Modified: 27 Mar 2006 13:58
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

[22 Mar 2006 9:47] Jonas Oreland
When one gets timeout in ABORT handling, typically due to nodefailure
  if transaction had more than 32 operations, and one got another timeout
  during the abort, this could in some circumstances result in a node failure.

How to repeat:

Suggested fix:
[22 Mar 2006 10:46] 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:

[24 Mar 2006 12:28] Jonas Oreland
pushed into 5.1.8
[27 Mar 2006 10:12] Jonas Oreland
pushed into 5.0.20
[27 Mar 2006 12:04] Jonas Oreland
pushed into 4.1.19
[27 Mar 2006 13:58] 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 4.1.19, 5.0.20, and 5.1.8 changelogs. Closed.