[
https://issues.apache.org/jira/browse/IGNITE-2854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15245244#comment-15245244
]
Semen Boikov commented on IGNITE-2854:
--------------------------------------
Andrey,
I have comments regarding TransactionDeadlockException:
- it should be placed in 'org.apache.ignite.transactions' package and extend
IgniteException, also please add some javadoc explaining when it can be thrown
- we need to add it in 'throws' clause and javadoc for all
org.apache.ignite.transactions.Transaction's, IgniteCache methods where it can
be thrown. I also see that others transactions exceptions
(TransactionTimeoutException, TransactionRollbackException,
TransactionOptimisticException, TransactionHeuristicException) are not declared
in 'throws' and javadoc, please fix it as well as part of this ticket.
> 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)
