ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Sapezhko (JIRA)" <j...@apache.org>
Subject [jira] [Created] (IGNITE-8167) Recovery after crash sometimes leads to starting from beginning absolute wal segment index
Date Fri, 06 Apr 2018 14:36:00 GMT
Pavel Sapezhko created IGNITE-8167:
--------------------------------------

             Summary: 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
             Fix For: 2.5


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)

Mime
View raw message