Bug #27005 Node failure + API failure can crash SUMA resend
Submitted: 9 Mar 2007 16:29 Modified: 23 Mar 2007 11:55
Reporter: Jonas Oreland
Status: Closed
Category:Server: ClusterRep Severity:S3 (Non-critical)
Version: OS:
Assigned to: Jonas Oreland Target Version:

[9 Mar 2007 16:29] Jonas Oreland 
Description:
crash node at approxiatly same time as crashing a mysqld
the resend algorithm will scan all buffers and resend them :-)

but the crash of the mysqld can cause the subsrcribtion to be removed
  and the table-objects to also be remove...
  so the resend will the derefence a uninitialized table.

How to repeat:
.

Suggested fix:
.
[14 Mar 2007 18:43] 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/21918

ChangeSet@1.2434, 2007-03-14 15:37:47+01:00, jonas@perch.ndb.mysql.com +2 -0
  ndb - bug#27005
      Handle API failure during resend
      API failure could cause release of table object, which will make resend crash
        when dereferencing table object
        
      Solution, use table_id+hash+schemaversion instead of *raw* pointer in resend
[14 Mar 2007 18:54] 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/21924

ChangeSet@1.2117, 2007-03-14 14:51:31+01:00, jonas@perch.ndb.mysql.com +1 -0
  ndb - bug#27005 (wl2325-5.0)
      Handle API failure during resend
      API failure could cause release of table object, which will make resend crash
        when dereferencing table object
      
      Solution, use table_id+hash+schemaversion instead of *raw* pointer in resend
[22 Mar 2007 21:20] Mads Martin Joergensen 
Fixed in 5.1.17
[23 Mar 2007 11:55] 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.17  changelog.