[
https://issues.apache.org/jira/browse/IGNITE-11789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Chudov updated IGNITE-11789:
----------------------------------
Description:
When LRT is detected, in the case if it is active, local node creates a request
to near (client) node to get the dump of a thread that created the transaction.
Dump of the client node appears in server node log.
There is new property in org.apache.ignite.mxbean.TransactionsMXBean class that
shows is thread dumps requesting allowed or disallowed:
*TxOwnerDumpRequestsAllowed*
By default, dump requests are turned on.
Log messages look like following:
{code:java}
Dumping the near node thread that started transaction [xidVer=<xidVer>]
Stack trace of the transaction owner thread:
<stack trace from client node>
{code}
In case of client error or error while trying to read result:
{code:java}
Could not get thread dump from transaction owner near node:
<stack trace>{code}
In case of error while trying to send request:
{code:java}
Could not send dump request to transaction owner near node:
<stack trace>
{code}
In case if client is already out of topology:
{code:java}
Could not get thread dump from transaction owner because near node is now out
of topology. Node ID: <node id>{code}
In case if client does not support this feature:
{code:java}
Could not send dump request to transaction owner near node: node does not
support this feature.
{code}
was:
When LRT is detected, in the case if it is active, local node creates a request
to near (client) node to get the dump of a thread that created the transaction.
Dump of the client node appears in server node log.
There are methods in org.apache.ignite.mxbean.TransactionsMXBean class to allow
and disallow thread dumps requesting:
public boolean getTxOwnerDumpRequestsAllowed() - to get information about
whether requesting is allowed;
public void setTxOwnerDumpRequestsAllowed(boolean allowed) - to allow and
disallow dump requests.
By default, dump requests are turned on.
> Document changes of LRT diagnostic messages made in IGNITE-11392
> ----------------------------------------------------------------
>
> Key: IGNITE-11789
> URL: https://issues.apache.org/jira/browse/IGNITE-11789
> Project: Ignite
> Issue Type: Task
> Components: documentation
> Reporter: Denis Chudov
> Priority: Major
> Fix For: 2.8
>
>
> When LRT is detected, in the case if it is active, local node creates a
> request to near (client) node to get the dump of a thread that created the
> transaction. Dump of the client node appears in server node log.
> There is new property in org.apache.ignite.mxbean.TransactionsMXBean class
> that shows is thread dumps requesting allowed or disallowed:
> *TxOwnerDumpRequestsAllowed*
> By default, dump requests are turned on.
> Log messages look like following:
>
> {code:java}
> Dumping the near node thread that started transaction [xidVer=<xidVer>]
> Stack trace of the transaction owner thread:
> <stack trace from client node>
> {code}
> In case of client error or error while trying to read result:
>
>
> {code:java}
> Could not get thread dump from transaction owner near node:
> <stack trace>{code}
> In case of error while trying to send request:
>
>
> {code:java}
> Could not send dump request to transaction owner near node:
> <stack trace>
> {code}
> In case if client is already out of topology:
> {code:java}
> Could not get thread dump from transaction owner because near node is now out
> of topology. Node ID: <node id>{code}
> In case if client does not support this feature:
>
> {code:java}
> Could not send dump request to transaction owner near node: node does not
> support this feature.
> {code}
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
