[
https://issues.apache.org/jira/browse/IGNITE-13912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17292807#comment-17292807
]
shivakumar commented on IGNITE-13912:
-------------------------------------
Hi [~ktkale...@gridgain.com]
It is very difficult to handle all the scenario to reproduce this issue as part
of unit test,
this is a stability test (a sql client ingesting large data) run on ignite
cluster and visor has to connect and disconnect in-between to reproduce this
WAL overflow issue.
If you have any suggestions or if you can join zoom call with me it will be a
great help!
> 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: config.properties, ignite-config, reproducer.zip,
> server1-full-wal-checkpoint.log, wal-checkpoint-logs, wal_dir_contents,
> wal_grows_from_peak.PNG, wal_issue_reproduced.PNG, wal_usage.PNG,
> wal_usage_dec12.PNG, wal_usage_dec22nd_binary.PNG
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> 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)
