[
https://issues.apache.org/jira/browse/IGNITE-2854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15233174#comment-15233174
]
Andrey Gura commented on IGNITE-2854:
-------------------------------------
Removed redundant messages for synchronization awaiting for finishing of
deadlock detection. {{GridDhtLockFuture}} just doesn't release locks on
{{onTimeout}} invocation. Locks will be release during transaction rolling back.
Detection process is asynchronous now and doesn't block any thread.
It makes sense to implement detection for near cache and optimistic
transactions separately. Created IGNITE-2968 and IGNITE-2969.
> 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)
