ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Semen Boikov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-2854) Need to implement deadlock detection
Date Thu, 21 Apr 2016 06:34:25 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-2854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15251374#comment-15251374

Semen Boikov commented on IGNITE-2854:

I reviewed last changes, did some changes, please take a look. Have some more comments:
- after you changed 'directType' for messages code in DeadlockDetectionListener.processFailedMessage
is broken, please fix and add test
- let's add sanity check in tests that IgniteTxManager.deadlockDetectFuts on all nodes is
empty at the end

> Need to implement deadlock detection
> ------------------------------------
>                 Key: IGNITE-2854
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2854
>             Project: Ignite
>          Issue Type: New Feature
>          Components: cache
>    Affects Versions: 1.5.0.final
>            Reporter: Valentin Kulichenko
>            Assignee: Andrey Gura
>             Fix For: 1.6
> Currently, if transactional deadlock occurred, there is no easy way to find out which
locks were reordered.
> We need to add a mechanism that will collect information about awating candidates, analyze
it and show guilty keys. Most likely this should be implemented with the help of custom discovery
> In addition we should automatically execute this mechanism if transaction times out and
add information to timeout exception.

This message was sent by Atlassian JIRA

View raw message