[
https://issues.apache.org/jira/browse/IGNITE-11059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16777942#comment-16777942
]
Alexei Scherbakov commented on IGNITE-11059:
--------------------------------------------
[~agoncharuk], I agree, dumping first not yet locked key should be enough for
detecting tx blocker.
Actually the same thing should be done for
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture#lockKeys.
> Print information about pending locks queue in case of dht local tx timeout.
> ----------------------------------------------------------------------------
>
> Key: IGNITE-11059
> URL: https://issues.apache.org/jira/browse/IGNITE-11059
> Project: Ignite
> Issue Type: Improvement
> Reporter: Alexei Scherbakov
> Assignee: Ivan Daschinskiy
> Priority: Major
> Labels: newbie
> Fix For: 2.8
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Currently in case of dht local tx timeout it's hard to understand which keys
> was not locked.
> Addtional information should be printed in log on timeout containing
> information about pending keys:
> key, tx info holding a lock (xid, label if present)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
