[
https://issues.apache.org/jira/browse/IGNITE-8610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Kovalenko updated IGNITE-8610:
Description:
After implementation IGNITE-6411 and IGNITE-8087 we can face with situation
when after some checkpoint, WAL was temporarily disabled and enabled again. In
this case we can't treat that checkpoint as start point to rebalance, because
WAL history after such checkpoint may contain gaps.
We should rework our checkpoint / wal history searching mechanism and ignore
such checkpoints.
was:
After implementation IGNITE-6411 and IGNITE-8087 we can face with situation
when after some checkpoint, WAL was temporarily disabled and enabled again. In
this case we can't treat such checkpoint as start point to rebalance, because
WAL history after such checkpoint may contain gaps.
We should rework our checkpoint / wal history searching mechanism and ignore
such checkpoints.
> Searching checkpoint / WAL history for rebalancing is not properly working in
> case of local/global WAL disabling
>
>
> Key: IGNITE-8610
> URL: https://issues.apache.org/jira/browse/IGNITE-8610
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.5
>Reporter: Pavel Kovalenko
>Assignee: Pavel Kovalenko
>Priority: Major
> Fix For: 2.6
>
>
> After implementation IGNITE-6411 and IGNITE-8087 we can face with situation
> when after some checkpoint, WAL was temporarily disabled and enabled again.
> In this case we can't treat that checkpoint as start point to rebalance,
> because WAL history after such checkpoint may contain gaps.
> We should rework our checkpoint / wal history searching mechanism and ignore
> such checkpoints.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
