[
https://issues.apache.org/jira/browse/IGNITE-8167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16463892#comment-16463892
]
Pavel Sapezhko commented on IGNITE-8167:
----------------------------------------
Hi, "I think there is ticket in the scope to fix behavior of case of
`restore == null`." What ticket did you talk about?
On Thu, May 3, 2018 at 3:43 PM Dmitriy Pavlov (JIRA) <[email protected]>
--
С уважением,
Cапежко Павел Александрович
Инженер-программист ООО "Synesis"
Skype: p.sapezhko
> 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)
