[
https://issues.apache.org/jira/browse/IGNITE-13847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17249566#comment-17249566
]
Ignite TC Bot commented on IGNITE-13847:
----------------------------------------
{panel:title=Branch: [pull/8576/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8576/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5791020&buildTypeId=IgniteTests24Java8_RunAll]
> Make GridEncryptionManager#onWalSegmentRemoved async
> ----------------------------------------------------
>
> Key: IGNITE-13847
> URL: https://issues.apache.org/jira/browse/IGNITE-13847
> Project: Ignite
> Issue Type: Improvement
> Components: persistence
> Reporter: Kirill Tkalenko
> Assignee: Kirill Tkalenko
> Priority: Major
> Labels: IEP-18
> Fix For: 2.10
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When implementing IGNITE-13831 I was faced with deadlock.
> When execute *FileWriteAheadLogManager#rollOver*, begin to clean WAL archive
> since we have reached the *DataStorageConfiguration#maxWalArchiveSize*, after
> deleting a segment, execute the *GridEncryptionManager#onWalSegmentRemoved*
> that wants to write to the metastore, but it will not succeed, since it will
> wait for *FileWriteAheadLogManager#rollOver*.
> I suggest making the *GridEncryptionManager#onWalSegmentRemoved* asynchronous
> in a separate pool, for example, as a *CacheGroupPageScanner#singleExecSvc*.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
