[jira] [Comment Edited] (IGNITE-6445) IgniteTxManager.txLocksInfo method misses locks

["Vitaliy Biryukov (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-6445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16187997#comment-16187997 ] 

Vitaliy Biryukov edited comment on IGNITE-6445 at 10/3/17 9:48 AM:
-------------------------------------------------------------------

[~agura], [Upsource Test|https://reviews.ignite.apache.org/ignite/review/IGNT-CR-355?filePath=/modules/core/src/test/java/org/apache/ignite/internal/processors/cache/transactions/TxOptimisticDeadlockDetectionTest.java]
TxOptimisticDeadlockDetectionTest#testDeadlocksPartitionedNearTxOnPrimary in my commit reproduce this bug with a probability of 99%(based on HashMap order).

GridNearTxLocal and GridNearTxLocal can contain different entries for the same key. And these entries are associated with different MVCC candidates. 
If GridNearTxLocal process first required MVCC candidates can be spiped.
{code:java}
if (res.txLocks(txKey) == null) {
.
.
.
}
{code}



was (Author: vitaliyb):
[~agura], [Upsource Test|https://reviews.ignite.apache.org/ignite/review/IGNT-CR-355?filePath=/modules/core/src/test/java/org/apache/ignite/internal/processors/cache/transactions/TxOptimisticDeadlockDetectionTest.java]
TxOptimisticDeadlockDetectionTest#testDeadlocksPartitionedNearTxOnPrimary in my commit reproduce this bug with a probability of 99%(based on HashMap order).


> IgniteTxManager.txLocksInfo method misses locks
> -----------------------------------------------
>
>                 Key: IGNITE-6445
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6445
>             Project: Ignite
>          Issue Type: Bug
>    Affects Versions: 2.2
>            Reporter: Vitaliy Biryukov
>            Assignee: Vitaliy Biryukov
>             Fix For: 2.3
>
>
> In some cases "IgniteTxManager.txLocksInfo" method (searches for locks) misses locks.
> For example:
> # In case of a configuration with near cache, entries are created for the near cache and for the ordinal cache. For each entry, their own MVCC candidates are created.
> # For non-custom objects of type (Integer, etc.), the entry stored in "GridNearTxLocal" is not associated with MVCC candidates with which the same entity is associated in another format stored in "GridDhtTxLocal"



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)