[IGNITE-8614] The atomic cache in inconsistent state

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.4
• Assignee: Unassigned
• Reporter: Denis Garus
• Created: 25/May/18 11:23
• Updated: 10/Oct/19 14:26

Description

Cache configuration:
CacheMode - PARTITIONED
Backups - 1
RebalanceMode - SYNC
WriteSynchronizationMode - FULL_ASYNC

There is a situation when the atomic cache becomes inconsistent.
There are two nodes: Node_1 with primary partition and Node_2 with backup partition.
1. Node_3 is started;
2. Before a rebalance of the partition from Node_1 to Node_3 is occurred new value is put to the partition on Node_1;
3. Node_1 creates a future for a propagating new value to Node_2 and Node_3;
4. Node_3 gets new value from Node_1 in the process a rebalance;
5. Node_1 is stopped;
6. The future from step 3 is failed because of step 5.
Now we have Node_3 with the new value and Node_2 with old value.

We need to find out the way to fix this inconsistent state and implement one.

The reproducer is in the attach.

Issue Links

• blocks: IGNITE-5979 [Test Failed] GridCacheAtomicInvalidPartitionHandlingSelfTest.testPrimaryFullAsync