[jira] [Created] (IGNITE-20641) Entries added via data streamer to persistent cache are not written to cache dump

["Sergey Korotkov (Jira)" <ji...@apache.org>]

Sergey Korotkov created IGNITE-20641:
----------------------------------------

             Summary: Entries added via data streamer to persistent cache are not written to cache dump
                 Key: IGNITE-20641
                 URL: https://issues.apache.org/jira/browse/IGNITE-20641
             Project: Ignite
          Issue Type: Bug
            Reporter: Sergey Korotkov


Steps to reproduce the problem:
 * start ignite with persistence
 * load some entries via the data streamer
 * restart ignite
 * create cache dump
 * check cache dump consistency

Consistency check would fail with errors like
{noformat}
[2023-10-11T12:13:28,711][INFO ][session=427e7c47][CommandHandlerLog] Hash conflicts:
[2023-10-11T12:13:28,721][INFO ][session=427e7c47][CommandHandlerLog] Conflict partition: PartitionKeyV2 [grpId=-1988013461, grpName=test-cache-1, partId=947]
[2023-10-11T12:13:28,725][INFO ][session=427e7c47][CommandHandlerLog] Partition instances: [PartitionHashRecordV2 [isPrimary=false, consistentId=ducker03, updateCntr=null, partitionState=OWNING, size=0, partHash=0, partVerHash=0], PartitionHashRecordV2 [isPrimary=false, consistentId=ducker02, updateCntr=null, partitionState=OWNING, size=48, partHash=731883010, partVerHash=0]]
{noformat}
*.dump files on primary are empty, but on backups are not.

---

Reason is that after ignite restart such records are always considered to be added after dump creation start in CreateDumpFutureTask::isAfterStart. That is because entries added via the datastreamer have version equal to isolatedStreamerVer but isolatedStreamerVer changes on each ignite restart and isolatedStreamerVer is always greater than startVer.




--
This message was sent by Atlassian Jira
(v8.20.10#820010)