[
https://issues.apache.org/jira/browse/IGNITE-2854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15244850#comment-15244850
]
Andrey Gura commented on IGNITE-2854:
-------------------------------------
Added the following system properties:
* {{IGNITE_TX_DEADLOCK_DETECTION_TIMEOUT}} - allows limit deadlock detection
time.
* {{IGNITE_TX_DEADLOCK_DETECTION_MAX_ITERS}} - allows limit the number of
iteration for performing deadlock detection (0 or less means that deadlock
detection disabled).
Simplified asynchronous request/response processing.
Added message processing in case of unmarshalling errors.
> 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)
