Mikhail Efremov created IGNITE-26983:
----------------------------------------
Summary: Enrich possible deadlock logs message with extra
information
Key: IGNITE-26983
URL: https://issues.apache.org/jira/browse/IGNITE-26983
Project: Ignite
Issue Type: Improvement
Reporter: Mikhail Efremov
*Description*
At the moment in case of potential deadlock situation we have such message:
{code:java}
java.util.concurrent.CompletionException:
org.apache.ignite.tx.TransactionException: IGN-TX-4 Failed to acquire a lock
due to a possible deadlock [locker=0198c472-5842-0004-bf35-349400000001,
holder=0198c472-5833-0008-bf35-349400000001] TraceId:5928be7d
{code}
There are issues:
# what exactly {{locker}} and {{holder}} there? (answer: transactions, the
locker one is trying to get a lock, and the holder one that already acquired
it, but it isn't obvious);
# what UUID is there and how they could help us? (answer: TXs' IDs, but it
still couldn't help us);
# we don't know what operation faced with this issue (we can try to find it
through a stacktrace, but code lines are diverging right along) not what type
of lock was issued;
# stacktrace itself is an issue, the message should be enough;
There is a proposal to add to the log message the follow information:
# lock type
# operation type
# resource type that is protected by the lock
# change locker/holder names
# remove stacktrace, just left the message
*Motivation*
We should make better and information rich logs in general and especially in
potential huge issues like potential deadlock state.
*Definition of done*
Described improvements are applied to the log message.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
