Bug #76207 | REDO log execution problem | ||
---|---|---|---|
Submitted: | 7 Mar 2015 10:09 | Modified: | 27 Mar 2015 13:40 |
Reporter: | Mikael Ronström | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S3 (Non-critical) |
Version: | 7.4.5 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[7 Mar 2015 10:09]
Mikael Ronström
[27 Mar 2015 13:40]
Jon Stephens
Documented fix as follows in the NDB 7.2.0, 7.3.9, and 7.4.5 changelogs: When performing a restart, it was sometimes possible to find a log end marker which had been written by a previous restart, and that should have been invalidated. Now when when searching for the last page to invalidate, the same search algorithm is used as when searching for the last page of the log to read. Closed.