[ 
https://issues.apache.org/jira/browse/IGNITE-24638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Denis Chudov updated IGNITE-24638:
----------------------------------
    Description: 
*Motivation*

Abandoned transactions are neither committed nor aborted, they still exist, and 
their locks can be seen. The transactions for the view can be collected not 
only from coordinators, but cluster-wide looking into transaction states map on 
every node.

The easiest way is the adding new system view: system.txmetadata, which would 
collect the transaction meta data from every node.

*Definition of done*

New system view system.metadata is added. It should be node view collecting tx 
metas from every node.

  was:
*Motivation*

Abandoned transactions are neither committed nor aborted, they still exist, and 
their locks can be seen. The transactions for the view should be collected not 
only from coordinators, but cluster-wide looking into transaction states map on 
every node.

*Definition of done*

Abandoned transactions can be seen in system.transactions.


> Abandoned transactions should be listed in system.transactions view 
> --------------------------------------------------------------------
>
>                 Key: IGNITE-24638
>                 URL: https://issues.apache.org/jira/browse/IGNITE-24638
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Denis Chudov
>            Priority: Major
>              Labels: ignite-3
>
> *Motivation*
> Abandoned transactions are neither committed nor aborted, they still exist, 
> and their locks can be seen. The transactions for the view can be collected 
> not only from coordinators, but cluster-wide looking into transaction states 
> map on every node.
> The easiest way is the adding new system view: system.txmetadata, which would 
> collect the transaction meta data from every node.
> *Definition of done*
> New system view system.metadata is added. It should be node view collecting 
> tx metas from every node.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to