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

Posted to dev@ignite.apache.org by "Alexey Goncharuk (JIRA)" <ji...@apache.org> on 2019/02/22 13:29:00 UTC

[jira] [Created] (IGNITE-11392) Improve LRT diagnostic messages

Alexey Goncharuk created IGNITE-11392:
-----------------------------------------

             Summary: Improve LRT diagnostic messages
                 Key: IGNITE-11392
                 URL: https://issues.apache.org/jira/browse/IGNITE-11392
             Project: Ignite
          Issue Type: Improvement
            Reporter: Alexey Goncharuk
             Fix For: 2.8


Currently we print out only local information about long-running transactions. This makes it hard to understand the cause of the LRT when an ACTIVE transaction is initiated by a client in a large system and is not being committed.
Given that a primary node knows the near node ID, we can send a diagnostic message to the near node for an ACTIVE transaction, find the thread that started the transaction and dump it's stack, so the server node logs can at least give an idea why the transaction is not being committed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)