[jira] [Commented] (IGNITE-6333) Improve cache transaction metrics to better understand transactions efficiency.
[ https://issues.apache.org/jira/browse/IGNITE-6333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16292160#comment-16292160 ] Pavel Pereslegin commented on IGNITE-6333: -- [~ascherbakov], take a look at this patch, please. > 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 > Fix For: 2.4 > > > 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)
[jira] [Commented] (IGNITE-6333) Improve cache transaction metrics to better understand transactions efficiency.
[ https://issues.apache.org/jira/browse/IGNITE-6333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16288847#comment-16288847 ] ASF GitHub Bot commented on IGNITE-6333: GitHub user xtern reopened a pull request: https://github.com/apache/ignite/pull/2883 IGNITE-6333 Improve cache transaction metrics to better understand transactions efficiency. You can merge this pull request into a Git repository by running: $ git pull https://github.com/xtern/ignite IGNITE-6333 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/2883.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2883 commit 78b312d73c947cd62af787838ce42fecf96f87d3 Author: Pereslegin Pavel Date: 2017-11-20T18:31:10Z IGNITE-6333 Added rollbacks due to deadlock/timeout tx metrics. commit 0dd91820e5bf017d408ff364cd3906d69b76df30 Author: Pereslegin Pavel Date: 2017-12-11T20:48:26Z IGNITE-6333 Removed unrelated changes, fixed test code style. commit 3c0c2153bbc753eac88bc99f6dde00108397c219 Author: Pavel Pereslegin <30606288+xt...@users.noreply.github.com> Date: 2017-12-12T07:56:29Z IGNITE-6333 Wrong Jira issue. > 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)
[jira] [Commented] (IGNITE-6333) Improve cache transaction metrics to better understand transactions efficiency.
[ https://issues.apache.org/jira/browse/IGNITE-6333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16288846#comment-16288846 ] ASF GitHub Bot commented on IGNITE-6333: Github user xtern closed the pull request at: https://github.com/apache/ignite/pull/2883 > 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)
[jira] [Commented] (IGNITE-6333) Improve cache transaction metrics to better understand transactions efficiency.
[ https://issues.apache.org/jira/browse/IGNITE-6333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16287390#comment-16287390 ] 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)
[jira] [Commented] (IGNITE-6333) Improve cache transaction metrics to better understand transactions efficiency.
[ 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)
