[
https://issues.apache.org/jira/browse/IGNITE-11392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-11392:
-------------------------------------
Ignite Flags: Docs Required,Release Notes Required (was: Docs Required)
> Improve LRT diagnostic messages
> -------------------------------
>
> Key: IGNITE-11392
> URL: https://issues.apache.org/jira/browse/IGNITE-11392
> Project: Ignite
> Issue Type: Improvement
> Reporter: Alexey Goncharuk
> Assignee: Denis Chudov
> Priority: Major
> Fix For: 2.8
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> 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
(v8.3.4#803005)
