[
https://issues.apache.org/jira/browse/IGNITE-13912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17255110#comment-17255110
]
shivakumar edited comment on IGNITE-13912 at 12/28/20, 7:32 AM:
----------------------------------------------------------------
You can see in the first graph (stability run which is started before Dec 12th
) there is a spike in WAL usage and when i again test with
https://issues.apache.org/jira/browse/IGNITE-12892 code merge, i didn't see any
WAL overflow (Not sure which code resolved it), but now again from Dec 23rd WAL
usage is not in limit(second graph)
was (Author: shm):
You can see in the first graph (stability run which is started before Dec 12th
) there is a spike in WAL usage and when i again test with
https://issues.apache.org/jira/browse/IGNITE-12892 code merge, i didn't see any
WAL overflow (Not sure which code resolved it), but now again from Dec 23rd WAL
usage is not in limit.
> 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
>
> Attachments: wal_usage_dec12.PNG, wal_usage_dec22nd_binary.PNG
>
>
> 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)
