[
https://issues.apache.org/jira/browse/IGNITE-13912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17254846#comment-17254846
]
Kirill Tkalenko commented on IGNITE-13912:
------------------------------------------
Hi, [~shm]! I tried to go back to
[commit|https://github.com/apache/ignite/commit/54ef8b804a6e9ec4edd95a367e19ebb768c36b07]
and found that we are exceeded *DataStorageConfiguration#maxWalArchiveSize* by
many times too. Previously, clearing WAL archive happened synchronously with
the completion of the checkpoint, now it happens asynchronously in a separate
thread, which also depends on the checkpoints. Now the mistake is that we often
delete and in small portions, or we can do it less often, but delete more.
> Incorrect calculation of WAL segments that should be deleted from WAL archive
> -----------------------------------------------------------------------------
>
> Key: IGNITE-13912
> URL: https://issues.apache.org/jira/browse/IGNITE-13912
> Project: Ignite
> Issue Type: Bug
> Components: persistence
> Reporter: Kirill Tkalenko
> Assignee: Kirill Tkalenko
> Priority: Critical
> Fix For: 2.10
>
>
> Now there is an incorrect calculation of WAL segments that should be deleted
> from WAL archive. Since we delete only those segments whose total size should
> not exceed *DataStorageConfiguration#maxWalArchiveSize *
> IGNITE_THRESHOLD_WAL_ARCHIVE_SIZE_PERCENTAGE*, but should be up to
> DataStorageConfiguration#maxWalArchiveSize *
> IGNITE_THRESHOLD_WAL_ARCHIVE_SIZE_PERCENTAGE*. Therefore, an excess of
> *DataStorageConfiguration#maxWalArchiveSize* occurs.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
