You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Andrey Gura (JIRA)" <ji...@apache.org> on 2016/03/22 22:54:25 UTC
[jira] [Assigned] (IGNITE-2854) Need to implement deadlock
detection
[ https://issues.apache.org/jira/browse/IGNITE-2854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrey Gura reassigned IGNITE-2854:
-----------------------------------
Assignee: Andrey Gura (was: Valentin Kulichenko)
> 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)