[
https://issues.apache.org/jira/browse/IGNITE-17122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17554058#comment-17554058
]
Kirill Tkalenko commented on IGNITE-17122:
------------------------------------------
[~marcus.lo] Please add:
* Configuration *org.apache.ignite.configuration.DataStorageConfiguration* in
xml format;
* More logs, at least to include information about checkpoints.
> Failed to release WAL segments even after reaching
> DataStorageConfiguration#maxWalArchiveSize
> ---------------------------------------------------------------------------------------------
>
> Key: IGNITE-17122
> URL: https://issues.apache.org/jira/browse/IGNITE-17122
> Project: Ignite
> Issue Type: Bug
> Components: persistence
> Affects Versions: 2.13
> Reporter: Marcus Lo
> Priority: Major
> Attachments: 1654590690_34713_920D9DE6-1C3F-4E8B-8181-446CB340ACF3.txt
>
>
> When maxWalArchiveSize is reached, Ignite is able to detect that and tries to
> release WAL segments (and prints out "maximum size of the WAL archive
> exceeded, the segments will be forcibly released"). However the WAL archive
> deletion doesn't happens immediately, and sometimes it happens almost 1 hour
> after the first detection, and the actual WAL archive size is much larger
> than the maxWalArchiveSize. See the (trimmed) attached log for an example.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
