ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Pereslegin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-6333) Improve cache transaction metrics to better understand transactions efficiency.
Date Tue, 12 Dec 2017 10:10:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-6333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16287387#comment-16287387
] 

Pavel Pereslegin commented on IGNITE-6333:
------------------------------------------

@ascherbakov, in common case deadlock detection starts if timeout was expired.
If timeout and deadlock are detected, do we need to count only deadlocks or both?

> Improve cache transaction metrics to better understand transactions efficiency.
> -------------------------------------------------------------------------------
>
>                 Key: IGNITE-6333
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6333
>             Project: Ignite
>          Issue Type: Improvement
>    Affects Versions: 2.0
>            Reporter: Alexei Scherbakov
>            Assignee: Pavel Pereslegin
>              Labels: cache, newbie
>
> I suggest to add:
> 1. Count of rollbacks due to transaction timeout. Depends on IGNITE-6181
> 2. Count of rollbacks due to deadlocks.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message