[
https://issues.apache.org/jira/browse/IGNITE-6445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16251616#comment-16251616
]
Vitaliy Biryukov commented on IGNITE-6445:
------------------------------------------
Hi, [~agura].
My first solution was bad.
It is enough to fix method {{GridNearOptimisticTxPrepareFuture#requestedKeys}}.
It can return keys requested from the local node, and if {{GridNearTxLocal}}
is process first, then locks from {{GridDhtTxLocal}} can be lost.
Please take a look at my new solution.
Actual PR, TC run, and Upsourse review are in *Issue Links*.
> 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.4
>
>
> 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)
