GitHub user amelius0712 opened a pull request:
https://github.com/apache/ignite/pull/3771 IGNITE-8167: Fix inconsistent last record pointer in case of recovery from corrupted WAL
Let's look at this peace of code from GridCacheDatabaseSharedManager.readCheckpointAndRestoreMemory
`
WALPointer restore = restoreMemory(status);
// First, bring memory to the last consistent checkpoint state if needed.
// This method should return a pointer to the last valid record in the WAL.
cctx.wal().resumeLogging(restore);
`
In case of `restore == null`. Logging will be resuming from 0 absolute WAL index.
You can merge this pull request into a Git repository by running:
$ git pull
https://github.com/Synesis-LLC/ignite ignite-8167
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/3771.patchTo close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3771
----
commit 40b9c8e227783f8d90fff5f2db4688e63be3dd37
Author: Pavel Sapezhko <pavel.sapezhko@...>
Date: 2018-04-06T14:36:23Z
IGNITE-8167: Fix inconsistent last record pointer in case of recovery from corrupted WAL
----
---
Locked
