[IGNITE-11242] Update counters mismatch after loading data via DataStreamer into MVCC-enabled caches

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Won't Fix
• Affects Version/s: 2.7
• Component/s: mvcc, streaming
• Assignee: Ivan Pavlukhin
• Reporter: Ivan Artiukhov
• Created: 07/Feb/19 10:11
• Updated: 11/Mar/19 08:13
• Resolved: 11/Mar/19 08:13

Description

Steps:
Start 1000 caches in 100 cache groups. Caches configuration:

                    <property name="atomicityMode" value="TRANSACTIONAL_SNAPSHOT"/>
                    <property name="backups" value="2"/>
                    <property name="cacheMode" value="PARTITIONED"/>
                    <property name="writeSynchronizationMode" value="FULL_SYNC"/>
                    <property name="partitionLossPolicy" value="READ_WRITE_SAFE"/>

Preload 10000 keys into each cache using DataStreamer
Run VerifyBackupPartitionsTaskV2 to check partition inconsistencies between hashes or update counters

Expected:
There are no differences between primary and backup partitions

Actual:
Two or three backup partitions in each cache group have update counters which differ from corresponding primary partitions. E.g.:

[2019-02-07 11:04:23,286][INFO ][Task-threadNum-0] Conflict partition: PartitionKeyV2 [grpId=-1093321804, grpName=cache_group_100, partId=261]
[2019-02-07 11:04:23,286][INFO ][Task-threadNum-0] Partition instances: [PartitionHashRecordV2 [isPrimary=true, consistentId=id-0, updateCntr=100, size=100, partHash=665729765], PartitionHashRecordV2 [isPrimary=false, consistentId=id-1, updateCntr=91, size=100, partHash=665729765], PartitionHashRecordV2 [isPrimary=false, consistentId=id-2, updateCntr=100, size=100, partHash=665729765]]

Issue Links

• Blocked: IGNITE-9314 MVCC TX: Datastreamer operations
• is related to: IGNITE-9314 MVCC TX: Datastreamer operations