You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Dmitry Pavlov (Jira)" <ji...@apache.org> on 2022/07/11 11:33:00 UTC

[jira] [Resolved] (IGNITE-9905) After transaction load cluster inconsistent

     [ https://issues.apache.org/jira/browse/IGNITE-9905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dmitry Pavlov resolved IGNITE-9905.
-----------------------------------
    Resolution: Cannot Reproduce

Presented information is not sufficient for reproducing the issue.

Most likely the issue was fixed as a part of another ticket.

Resolving the issue as Can't reproduce. Feel free to reopen if it is likely that the bug is still there

> After transaction load cluster inconsistent
> -------------------------------------------
>
>                 Key: IGNITE-9905
>                 URL: https://issues.apache.org/jira/browse/IGNITE-9905
>             Project: Ignite
>          Issue Type: Bug
>          Components: persistence
>    Affects Versions: 2.7
>            Reporter: ARomantsov
>            Priority: Critical
>              Labels: ise
>
> Loaded data into the cluster using transactions consisting of two get / two put
> Test env: one server, two server node, one client
> {code:java}
> idle_verify check has finished, found 60 conflict partitions: [counterConflicts=45, hashConflicts=15]
> Update counter conflicts:
> Conflict partition: PartitionKeyV2 [grpId=-1903385190, grpName=CACHEGROUP_PARTICLE_1, partId=98]
> Partition instances: [PartitionHashRecordV2 [isPrimary=true, consistentId=node2, updateCntr=1519, size=596, partHash=-1167688484], PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=1520, size=596, partHash=-1167688484]]
> Conflict partition: PartitionKeyV2 [grpId=-1903385190, grpName=CACHEGROUP_PARTICLE_1, partId=34]
> Partition instances: [PartitionHashRecordV2 [isPrimary=false, consistentId=node2, updateCntr=1539, size=596, partHash=-99631005], PartitionHashRecordV2 [isPrimary=true, consistentId=node1, updateCntr=1537, size=596, partHash=-1284437377]]
> Conflict partition: PartitionKeyV2 [grpId=770187303, grpName=CACHEGROUP_PARTICLE_1, partId=31]
> Partition instances: [PartitionHashRecordV2 [isPrimary=true, consistentId=node2, updateCntr=15, size=4, partHash=-1125172674], PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=16, size=4, partHash=-1125172674]]
> Conflict partition: PartitionKeyV2 [grpId=-1903385190, grpName=CACHEGROUP_PARTICLE_1, partId=39]
> Partition instances: [PartitionHashRecordV2 [isPrimary=true, consistentId=node2, updateCntr=1555, size=596, partHash=-40303136], PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=1556, size=596, partHash=-40303136]]
> Conflict partition: PartitionKeyV2 [grpId=-1903385190, grpName=CACHEGROUP_PARTICLE_1, partId=90]
> Partition instances: [PartitionHashRecordV2 [isPrimary=false, consistentId=node2, updateCntr=1557, size=596, partHash=-1295145299], PartitionHashRecordV2 [isPrimary=true, consistentId=node1, updateCntr=1556, size=596, partHash=-1221175703]]
> ...
> {code}



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