[
https://issues.apache.org/jira/browse/IGNITE-6442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16173051#comment-16173051
]
Vitaliy Biryukov edited comment on IGNITE-6442 at 9/20/17 11:46 AM:
--------------------------------------------------------------------
Hi, [~agura]. Please, review this issue.
[Upsourse|https://reviews.ignite.apache.org/ignite/review/IGNT-CR-346]
I've reproduced the case in which DD is not called and fixed bug. My test
method checks only that DD was called, but does not verify that it worked
correctly. Because in this case DD works flaky. I'll fix it at
[IGNITE-6445|https://issues.apache.org/jira/browse/IGNITE-6445] and add
correctness check to my test method.
[TC
run|https://ci.ignite.apache.org/viewLog.html?buildId=840419&tab=buildResultsDiv&buildTypeId=Ignite20Tests_RunAll]
was (Author: vitaliyb):
Hi, [~agura]. Please, review this issue.
[Upsourse|https://reviews.ignite.apache.org/ignite/review/IGNT-CR-346]
I've reproduced the case in which DD is not called and fixed bug. My test
method checks only that DD was called, but does not verify that it worked
correctly. Because in this case DD works flaky. I'll fix it at
[IGNITE-6445|https://issues.apache.org/jira/browse/IGNITE-6445] and add
correctness check to my test method.
> 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)
