You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Ivan Kapralov (JIRA)" <ji...@apache.org> on 2018/04/26 14:25:00 UTC

[jira] [Updated] (IGNITE-8402) Long running transaction JMX

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

Ivan Kapralov updated IGNITE-8402:
----------------------------------
    Description: 
Facing necessity in Long Running Transactions JMX metric implementation.

Needed: transaction start time, node ID, duration, cache full qualified name, originator ID.

 

  was:
Facing necessity in Long Running Transactions JMX metric implementation.

Needed: transaction start time, node ID, duration, cache ID, originator ID comma separated in the same string. Info about transactions that are hung up for more than 600 sec.

 


> Long running transaction JMX
> ----------------------------
>
>                 Key: IGNITE-8402
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8402
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql
>    Affects Versions: 2.4
>            Reporter: Ivan Kapralov
>            Priority: Major
>             Fix For: None
>
>
> Facing necessity in Long Running Transactions JMX metric implementation.
> Needed: transaction start time, node ID, duration, cache full qualified name, originator ID.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)