[
https://issues.apache.org/jira/browse/IGNITE-6445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16251453#comment-16251453
]
ASF GitHub Bot commented on IGNITE-6445:
----------------------------------------
GitHub user BiryukovVA opened a pull request:
https://github.com/apache/ignite/pull/3032
IGNITE-6445: Solution 1.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/BiryukovVA/ignite IGNITE-6527_firstSolution
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/3032.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3032
----
commit 262f6ab020a067f6e3982ac6073b3781b59d7615
Author: Vitaliy Biryukov <[email protected]>
Date: 2017-10-03T13:41:18Z
IGNITE-6445: Bug fixed.
----
> 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)
