Bug #22893 Unable to find REDO for frag during SR leaves frag empty, making DB inconsistent

Description:
 

How to repeat:
 

Suggested fix:

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/13264

ChangeSet@1.2550, 2006-10-06 16:05:46+02:00, jonas@perch.ndb.mysql.com +2 -0
  ndb - bug#22893
    Add checking of REDO to earlier during SR
        so take-over of node can be performed
        if it can't be restarted using logs
        (which btw is really weird...as it _should_ be able to use logs of other node in node group)
  
    Otherwise cluster could be started and 1 fragment on one node could not have been restored
    Making the cluster inconsisten, VERY BAD

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/13377

ChangeSet@1.2057, 2006-10-10 10:42:26+02:00, jonas@perch.ndb.mysql.com +2 -0
  ndb - bug#22893
      Add checking of REDO to earlier during SR
          so take-over of node can be performed
          if it can't be restarted using logs
          (which btw is really weird...as it _should_ be able to use logs of other node in node group)
  
    recommit in mysql-5.1-wl2325-5.0

pushed into 4.1.22

pushed into 5.0.29

pushed into 5.1.13

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 for 4.1.22/5.0.29/5.1.12.

*Fix for 5.0 documented in 5.0.30 Release Notes.*