[
https://issues.apache.org/jira/browse/IGNITE-11392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16805885#comment-16805885
]
Ignite TC Bot commented on IGNITE-11392:
----------------------------------------
{panel:title=--> Run :: All: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3456073&buildTypeId=IgniteTests24Java8_RunAll]
> 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: 10m
> 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
(v7.6.3#76005)
