[IGNITE-14516] WAL can continue to log into archived segment if auto rollover enabled

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Nikolay Izhikov
• Reporter: Nikolay Izhikov
• Created: 12/Apr/21 08:50
• Updated: 09/Oct/23 16:42
• Resolved: 31/Aug/23 19:44

Description

Currently, there is a possibility that WAL will continue to log into an archived segment after node restart.

Bug scenario:

1. WalAutoArchiveAfterInactivity enabled.
2. Node is stopping with the G.stop("ign", false").
3. T0: Performs last checkpoint write some records to current WAL segment(Segment#0) and freeze.
4. T1: Auto rollover happens in FileWriteAheadLogManager#checkWalRolloverRequiredDuringInactivityPeriod.
5. T2(FileArchiver) Archives Segment#0.

After restart, WAL will continue to log into Segment#0 which leads that newly logged data will not be archived after rollover because FileArchiver will wait for Segment#2 in SegmentCurrentStateStorage#waitNextSegmentForArchivation.

PR to highlight error - https://github.com/apache/ignite/pull/8997

It seems we should to continue to log into the next segment if curAbsIdx == lastArchivedSegment on start.

Issue Links

• duplicates: IGNITE-20097 WAL writes to an archived segment after node restart
• links to: GitHub Pull Request #9001