Bug #61500 | Rare bug in redo invalidation can lead to "Error while reading the REDO log" | ||
---|---|---|---|
Submitted: | 13 Jun 2011 11:27 | Modified: | 14 Jun 2011 14:16 |
Reporter: | Jonas Oreland | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S3 (Non-critical) |
Version: | 6.3.0 | OS: | Any |
Assigned to: | Jonas Oreland | CPU Architecture: | Any |
[13 Jun 2011 11:27]
Jonas Oreland
[13 Jun 2011 12:32]
Jonas Oreland
pushed to 6.3.45, 7.0.26 and 7.1.15
[14 Jun 2011 14:16]
Jon Stephens
Documented bugfix in the NDB 6.3.45, 7.0.26, and 7.1.15 changelogs, as follows: When global checkpoint indexes were written with no intervening end-of-file or megabyte border markers, this could sometimes lead to a situation in which the end of the redo log was mistakenly regarded as being between these GCIs, so that if the restart of a data node took place before the start of the next redo log was overwritten, the node encountered -Error while reading the REDO log-. Closed.