You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexei Scherbakov (JIRA)" <ji...@apache.org> on 2018/03/29 09:53:00 UTC
[jira] [Updated] (IGNITE-7910) Improve transaction debugging
support
[ https://issues.apache.org/jira/browse/IGNITE-7910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexei Scherbakov updated IGNITE-7910:
--------------------------------------
Description:
Currently there is no good means to debug problematic transactions without parsing cryptic logs on whole grid.
I suggest adding several improvents to mitigate the issue:
1. Add chaining method Transaction.withLabel(String) to attach transaction descrtiption.
2. Add method localActiveTransaction to IgniteTransactions interface, which will return all active near transactions for local node.
3. Extend control.sh to support retrieving active transactions information from grid nodes.
By default it shows N (specified by user) transactions ordered by longest duration.
For each transaction is shown:
Near node id(IP, hostname) / xid / state / duration / dht topology / meta from 1 if presents
It should support filtering by near node / state / duration and printing info for single tx if single xid is specified as argument.
In addition to that each transaction from the list may be forcibly rolled back by xid.
4. Add mbean with same functionality as in 3.
was:
Currently there is no good means to debug problematic transactions without parsing cryptic logs on whole grid.
I suggest adding several improvents to mitigate the issue:
1. Add chaining method Transaction.withMeta(String) to attach transaction descrtiption.
2. Add method localActiveTransaction to IgniteTransactions interface, which will return all active near transactions for local node.
3. Extend control.sh to support retrieving active transactions information from grid nodes.
By default it shows N (specified by user) transactions ordered by longest duration.
For each transaction is shown:
Near node id(IP, hostname) / xid / state / duration / dht topology / meta from 1 if presents
It should support filtering by near node / state / duration and printing info for single tx if single xid is specified as argument.
In addition to that each transaction from the list may be forcibly rolled back by xid.
4. Add mbean with same functionality as in 3.
> Improve transaction debugging support
> -------------------------------------
>
> Key: IGNITE-7910
> URL: https://issues.apache.org/jira/browse/IGNITE-7910
> Project: Ignite
> Issue Type: Improvement
> Affects Versions: 2.3
> Reporter: Alexei Scherbakov
> Priority: Major
> Fix For: 2.5
>
>
> Currently there is no good means to debug problematic transactions without parsing cryptic logs on whole grid.
> I suggest adding several improvents to mitigate the issue:
> 1. Add chaining method Transaction.withLabel(String) to attach transaction descrtiption.
> 2. Add method localActiveTransaction to IgniteTransactions interface, which will return all active near transactions for local node.
> 3. Extend control.sh to support retrieving active transactions information from grid nodes.
> By default it shows N (specified by user) transactions ordered by longest duration.
> For each transaction is shown:
> Near node id(IP, hostname) / xid / state / duration / dht topology / meta from 1 if presents
> It should support filtering by near node / state / duration and printing info for single tx if single xid is specified as argument.
> In addition to that each transaction from the list may be forcibly rolled back by xid.
> 4. Add mbean with same functionality as in 3.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)