Bug #29621 ndb_mgmd can timeout logevent request, making it to fail
Submitted: 7 Jul 2007 21:14 Modified: 15 Dec 2007 8:38
Reporter: Jonas Oreland Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version: OS:Any
Assigned to: Jonas Oreland CPU Architecture:Any
Triage: D4 (Minor)

[7 Jul 2007 21:14] Jonas Oreland
Description:
.

How to repeat:
.

Suggested fix:
.
[7 Jul 2007 21:17] 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:

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

ChangeSet@1.2158, 2007-07-07 23:15:58+02:00, jonas@perch.ndb.mysql.com +1 -0
  ndb - bug#29621 - setEventReportImpl can timeout
  1) remove retry from setEventReportImpl
  2) set retry in logevent thread
[23 Nov 2007 9:26] 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:

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

ChangeSet@1.2583, 2007-11-23 10:25:19+01:00, tomas@whalegate.ndb.mysql.com +1 -0
  Bug#29621 - ndb_mgmd can timeout logevent request, making it to fail
[14 Dec 2007 17:08] Bugs System
Pushed into 5.1.23-rc
[14 Dec 2007 17:09] Bugs System
Pushed into 6.0.5-alpha
[15 Dec 2007 8:38] 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 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.23 and 6.0.5 changelogs.