[
https://issues.apache.org/jira/browse/IGNITE-12551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolay Izhikov updated IGNITE-12551:
-------------------------------------
Fix Version/s: 2.8.1
> Partition desync if a partition is evicted then owned again and historically
> rebalanced
> ---------------------------------------------------------------------------------------
>
> Key: IGNITE-12551
> URL: https://issues.apache.org/jira/browse/IGNITE-12551
> Project: Ignite
> Issue Type: Bug
> Components: persistence
> Affects Versions: 2.7.6
> Reporter: Alexey Scherbakov
> Assignee: Alexey Scherbakov
> Priority: Major
> Fix For: 2.9, 2.8.1
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Where is a possibility of partition desync in the following scenario:
> 1. Some partition is evicted with non zero counters.
> 2. It is owned again and are going to be rebalanced.
> 3. Some node in a grid has history for the partition defined by it's
> (initial, current) counters pair.
> In this scenario the partition will be historically rebalanced having only
> partial data.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
