[
https://issues.apache.org/jira/browse/IGNITE-13831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko updated IGNITE-13831:
-------------------------------------
Description:
Users expect *DataStorageConfiguration#maxWalArchiveSize* to mean that WAL
archive will not exceed this value, but it is not.
It seems that to reduce the chance of getting into a situation when we exceed
WAL archive, it will be lowed when we clean it when switching to a new segment
than at the end of the checkpoint. It is proposed to move the archive cleanup
to *FileWriteAheadLogManager#rollOver* when the
*DataStorageConfiguration#maxWalArchiveSize* is reached.
was:
At the moment, WAL archive is cleared at the end of the checkpoint, which does
not seem correct and needs to be moved to the *FileWriteAheadLogManager*.
It is suggested to clear WAL archive in *FileWriteAheadLogManager#rollOver*
when the *DataStorageConfiguration#maxWalArchiveSize* is reached.
> Move WAL archive cleanup from checkpoint to rollover
> ----------------------------------------------------
>
> Key: IGNITE-13831
> URL: https://issues.apache.org/jira/browse/IGNITE-13831
> Project: Ignite
> Issue Type: Improvement
> Components: persistence
> Reporter: Kirill Tkalenko
> Assignee: Kirill Tkalenko
> Priority: Major
> Fix For: 2.10
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Users expect *DataStorageConfiguration#maxWalArchiveSize* to mean that WAL
> archive will not exceed this value, but it is not.
> It seems that to reduce the chance of getting into a situation when we exceed
> WAL archive, it will be lowed when we clean it when switching to a new
> segment than at the end of the checkpoint. It is proposed to move the archive
> cleanup to *FileWriteAheadLogManager#rollOver* when the
> *DataStorageConfiguration#maxWalArchiveSize* is reached.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
