[
https://issues.apache.org/jira/browse/IGNITE-10079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16671191#comment-16671191
]
Ivan Daschinskiy commented on IGNITE-10079:
-------------------------------------------
[~andrey-kuznetsov] Andrey, when I was implementing this feature,
[~ivan.glukos] asked me to maintain specific order. Let's me explain. Imagine
that 4 segments archived (0,1,2,3,4). But if segment # 4 is compressed first,
we must return -1. If segment 0 compressed after 4 , we must return 0. If
segment 3 is compressed then, we must return also 0. So if order of compression
is 4,0,1,3,2 we must return -1, 0, 1, 1, 4. [~ivan.glukos] can explain why this
specific order is so important
> FileWriteAheadLogManager may return invalid lastCompactedSegment
> ----------------------------------------------------------------
>
> Key: IGNITE-10079
> URL: https://issues.apache.org/jira/browse/IGNITE-10079
> Project: Ignite
> Issue Type: Bug
> Components: persistence
> Reporter: Andrey Kuznetsov
> Assignee: Andrey Kuznetsov
> Priority: Major
> Fix For: 2.8
>
> Attachments: WalCompactionAfterRestartTest.java
>
>
> As of current {{master}} branch,
> {{FileWriteAheadLogManager#lastCompactedSegment}} may report -1 even after
> some segments have been actually compressed. Reproducer is attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
