[
https://issues.apache.org/jira/browse/IGNITE-11059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16777860#comment-16777860
]
Alexey Goncharuk commented on IGNITE-11059:
-------------------------------------------
[~ivandasch] [~ascherbakov] Do we need to print out all the pending keys. When
lock future is used, we always acquire locks sequentially, so no need to print
out all keys, we need to print out only one key that actually blocks the lock
future and it's actual owner. If the number of keys in lock future is high, it
will complicate logs analysis.
WDYT?
> 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)
