[
https://issues.apache.org/jira/browse/IGNITE-12789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Bessonov updated IGNITE-12789:
-----------------------------------
Description:
org.apache.ignite.internal.processors.cache.persistence.tree.io.TrackingPageIO#resetCorruptFlag(long)
In order for tracking pages to work properly they should be persisted on disk,
it means that failed checkpoint scenario should be supported. Tracking pages
restoration has no associated WAL record so in that case binary recovery could
leave them broken after a valid repair.
was:
org.apache.ignite.internal.processors.cache.persistence.tree.io.TrackingPageIO#resetCorruptFlag(long)
In order for tracking pages to work properly they should be persisted on disk,
it means that failed checkpoint scenario should be supported. Tracking pages
restoration haЫ no associated WAL record so in that case binary recovery could
leave them broken after a valid repair.
> Tracking page repairing has no WAL record associated with it
> ------------------------------------------------------------
>
> Key: IGNITE-12789
> URL: https://issues.apache.org/jira/browse/IGNITE-12789
> Project: Ignite
> Issue Type: Bug
> Reporter: Ivan Bessonov
> Assignee: Ivan Bessonov
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> org.apache.ignite.internal.processors.cache.persistence.tree.io.TrackingPageIO#resetCorruptFlag(long)
>
> In order for tracking pages to work properly they should be persisted on
> disk, it means that failed checkpoint scenario should be supported. Tracking
> pages restoration has no associated WAL record so in that case binary
> recovery could leave them broken after a valid repair.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
