[
https://issues.apache.org/jira/browse/IGNITE-6442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16171924#comment-16171924
]
ASF GitHub Bot commented on IGNITE-6442:
----------------------------------------
GitHub user BiryukovVA opened a pull request:
https://github.com/apache/ignite/pull/2699
IGNITE-6442
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/BiryukovVA/ignite IGNITE-6442
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/2699.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 #2699
----
commit b2ee52f335c02211b3c26aab3eae708b6fe09cd9
Author: Vitaliy Biryukov <[email protected]>
Date: 2017-09-19T15:39:40Z
IGNITE-6442: Bug fixed.
----
> Deadlock detection doesn't execute.
> -----------------------------------
>
> Key: IGNITE-6442
> URL: https://issues.apache.org/jira/browse/IGNITE-6442
> Project: Ignite
> Issue Type: Bug
> Reporter: Vitaliy Biryukov
> Assignee: Vitaliy Biryukov
>
> In case of a configuration with near cache and if all entities of one of the
> transactions involved in the deadlock are on the node being the initiator of
> this transaction, then immediately after the timeout, the transaction rolls
> back (without calling DD).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
