Bug #51547 Cutting of REDO log is too conservative
Submitted: 26 Feb 2010 11:16 Modified: 26 Feb 2010 16:43
Reporter: Jonas Oreland Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:mysql-5.1-telco-6.3 OS:Any
Assigned to: Jonas Oreland CPU Architecture:Any
Tags: mysql-5.1-telco-6.3

[26 Feb 2010 11:16] Jonas Oreland 
Description:
When deciding how to cut REDO log, DIH saved more than was needed to restore
previous LCP, making it easier to run out of REDO (410)

How to repeat:
.

Suggested fix:
.
[26 Feb 2010 11:18] 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/101582

3105 Jonas Oreland	2010-02-26
      ndb - bug#51547 - only consider latest LCP when deciding hwo much to cut REDO-log
[26 Feb 2010 11:27] Jonas Oreland 
pushed to 6.3.32, 7.0.13 and 7.1.2
[26 Feb 2010 16:43] Jon Stephens 
Documented bugfix in the NDB-6.3.32, 7.0.13, and 7.1.2 changelogs, as follows:

        When deciding how to divide the REDO log, the DBDIH kernel block
        saved more than was needed to restore the previous local
        checkpoint, which could cause REDO log space to be exhausted
        prematurely (NDB error 410).

Closed.