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

Vitaliy Biryukov updated IGNITE-6445:
-------------------------------------
    Description: 
In some cases "IgniteTxManager.txLocksInfo" method (searches for locks) misses 
locks.
For example:
# In case of a configuration with near cache, entries are created in 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"

  was:
In some cases "IgniteTxManager.txLocksInfo" method (searches for locks) misses 
locks.
For example:
# In case of a configuration with near cache, entities 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"


> IgniteTxManager.txLocksInfo method misses locks
> -----------------------------------------------
>
>                 Key: IGNITE-6445
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6445
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Vitaliy Biryukov
>            Assignee: Vitaliy Biryukov
>
> In some cases "IgniteTxManager.txLocksInfo" method (searches for locks) 
> misses locks.
> For example:
> # In case of a configuration with near cache, entries are created in 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)

Reply via email to