[
https://issues.apache.org/jira/browse/IGNITE-11059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763609#comment-16763609
]
Alexei Scherbakov commented on IGNITE-11059:
--------------------------------------------
[~ivandasch]
Changes look good to me.
But probably it's worth adding newly introduced debug info directly to toString
implementation (both for DhtPrepare and DhtLock futures) and resort to already
existing code for printing long running operations.
[~agoncharuk] what do you think ?
> 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)
