[
https://issues.apache.org/jira/browse/IGNITE-13831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17246479#comment-17246479
]
shivakumar commented on IGNITE-13831:
-------------------------------------
Hi [[email protected]]
Is this ticket is just for moving WAL archive clean-up logic from "post
checkpoint" to *FileWriteAheadLogManager#rollOver ?* Or is there any plan to
change the logic which considers Archived WAL segments for clean-up ?
I'm facing a Major issue related to WAL usage and WAL usage growing infinitely
with heavy write load even maxWalArchiveSize is set.
Ref:
[http://apache-ignite-users.70518.x6.nabble.com/Could-not-clear-historyMap-due-to-WAL-reservation-on-cp-td34779.html]
[http://apache-ignite-users.70518.x6.nabble.com/connecting-to-visor-shell-permanently-stops-unwanted-WAL-clean-up-td34737.html]
with Thanks,
Shiva
> 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
>
>
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
