[
https://issues.apache.org/jira/browse/IGNITE-6894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16328635#comment-16328635
]
Anton Vinogradov commented on IGNITE-6894:
------------------------------------------
Currenly,
Ignite provide list of such TX on grid hang, see
\{{org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager#dumpLongRunningOperations0}}
for details.
> Hanged Tx monitoring
> --------------------
>
> Key: IGNITE-6894
> URL: https://issues.apache.org/jira/browse/IGNITE-6894
> Project: Ignite
> Issue Type: Improvement
> Reporter: Anton Vinogradov
> Assignee: Dmitriy Sorokin
> Priority: Major
> Labels: iep-7
> Fix For: 2.5
>
>
> Hanging Transactions not Related to Deadlock
> Description
> This situation can occur if user explicitly markups the transaction (esp
> Pessimistic Repeatable Read) and, for example, calls remote service (which
> may be unresponsive) after acquiring some locks. All other transactions
> depending on the same keys will hang.
> Detection and Solution
> This most likely cannot be resolved automatically other than rollback TX by
> timeout and release all the locks acquired so far. Also such TXs can be
> rolled back from Web Console as described above.
> If transaction has been rolled back on timeout or via UI then any further
> action in the transaction, e.g. lock acquisition or commit attempt should
> throw exception.
> Report
> Management tools (eg. Web Console) should provide ability to rollback any
> transaction via UI.
> Long running transaction should be reported to logs. Log record should
> contain: near nodes, transaction IDs, cache names, keys (limited to several
> tens of), etc ( ?).
> Also there should be a screen in Web Console that will list all ongoing
> transactions in the cluster including the info as above.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
