[
https://issues.apache.org/jira/browse/IGNITE-8167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16450048#comment-16450048
]
Dmitriy Govorukhin commented on IGNITE-8167:
--------------------------------------------
Your changes do not fix the problem, because if you have corrupted WAL record
after last success checkpoint, you cannot restore your partition data structure
to the consistent state (apply all binary delta record from previous successes
checkpoint to checkpoint which was crashed). It is an unrecoverable situation.
See more info in "Crash Recovery" section of [pds
underthehood|https://cwiki.apache.org/confluence/display/IGNITE/Ignite+Persistent+Store+-+under+the+hood#IgnitePersistentStore-underthehood-CrashRecovery].
We must detect this situation and stop node with an appropriate message.
> Recovery after crash sometimes leads to starting from beginning absolute wal
> segment index
> ------------------------------------------------------------------------------------------
>
> Key: IGNITE-8167
> URL: https://issues.apache.org/jira/browse/IGNITE-8167
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.4
> Environment: Doesn't meter. We saw these behavior in k8s deployment
> as in local deployment too. Using any of WAL_MOD.
> Reporter: Pavel Sapezhko
> Assignee: Pavel Sapezhko
> Priority: Major
> Fix For: 2.5
>
> Attachments: ignite_precrash.log
>
>
> When we are trying to restore after crash using wal log, sometimes we can
> find corrupted wal messages which can leads to starting from beginning
> absolute wal index. So, we will have broken wal archiver thread due to
> assertation error(but we still having working Ignite instance. I think we
> need to discuss if we are really want it) and as a result on next restart we
> can see "Wal history is too short" message.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
