[
https://issues.apache.org/jira/browse/IGNITE-8360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-8360:
-------------------------------------
Description:
Current implementation tries to recover corrupted page from WAL, potentially
scanning all archived segments [1]
If archive is very large, on example due to large history, this might take
significant time preventing cache start with consequences like hanging PME.
[1]
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl#tryToRestorePage
was:
Current implementation tries to recover corrupted page from WAL, potentially
scanning all archived segments [1]
If archive is very large, on example due to large history or enabled
point-in-time recovery, this might take significant time preventing cache start
with consequences like hanging PME.
[1]
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl#tryToRestorePage
> Page recovery from WAL can be very slow.
> ----------------------------------------
>
> Key: IGNITE-8360
> URL: https://issues.apache.org/jira/browse/IGNITE-8360
> Project: Ignite
> Issue Type: Improvement
> Components: persistence
> Affects Versions: 2.4
> Reporter: Alexei Scherbakov
> Priority: Major
> Fix For: 2.6
>
>
> Current implementation tries to recover corrupted page from WAL, potentially
> scanning all archived segments [1]
> If archive is very large, on example due to large history, this might take
> significant time preventing cache start with consequences like hanging PME.
> [1]
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl#tryToRestorePage
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
