You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Vladimir Steshin (Jira)" <ji...@apache.org> on 2023/05/01 15:21:00 UTC

[jira] [Created] (IGNITE-19389) Make lock acquiring timeout message more certain.

Vladimir Steshin created IGNITE-19389:
-----------------------------------------

             Summary: Make lock acquiring timeout message more certain.
                 Key: IGNITE-19389
                 URL: https://issues.apache.org/jira/browse/IGNITE-19389
             Project: Ignite
          Issue Type: Improvement
            Reporter: Vladimir Steshin


Suggestion: make text of lock acquiring timeout message more certain if there is no attempt to acquire lock

We've met a case when user sees lock acquiring timeout in transaction but is confused in researching the cause. He expected and tried to find concurrent transaction, deadlocks, hanging locks, etc. Actually, lock attempt hasn't even launched. The timeout has already happened. Stacktrace indicates the problem, but it is not the best solution to a user.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)