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 Wed, 20 Apr 2016 15:15:25 GMT

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

Semen Boikov commented on IGNITE-2854:
--------------------------------------

Some more comments:
- need add proper synchronization for TxDeadlockFuture.curNodeId access
- please change TxDeadlockFuture.futId from IgniteUuid to Long
- please add some basic test for deadlock exception messsage (check correctness of info about
keys' values, nodes, threads)

> 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
message.
> 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
(v6.3.4#6332)

Mime
View raw message