[
https://issues.apache.org/jira/browse/IGNITE-13831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17247919#comment-17247919
]
Pavel Pereslegin commented on IGNITE-13831:
-------------------------------------------
Hello [[email protected]].
As far as the proposal for asynchronous execution of onWalSegmentRemoved is
concerned, personally, I see no problem with such a change, but I think we can
use the system pool for this.
The only thing, it seems to me, we need to make a separate short check before
adding the task to the pool.
I prepared the draft patch for this change here:
[https://github.com/xtern/ignite/pull/44/files]
Can you do proposed changes in your PR or we need a separate ticket for this?
> 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
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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)
