[
https://issues.apache.org/jira/browse/IGNITE-10079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16671237#comment-16671237
]
Andrey Kuznetsov commented on IGNITE-10079:
-------------------------------------------
[~ivandasch], got it. And this ordering works perfectly.
There are still some possibilities to bring {{SegmentCompressStorage}} to
inconsistent state. For example, in the fix I proposed, I just mitigate
consequences of independent changes to {{SegmentAware.lastTruncatedArchiveIdx}}
and {{SegmentCompressStorage.compressingSegments}}. Is it possible to place
both into the same class and modify in atomic fashion?
> 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)
