You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexey Kuznetsov (JIRA)" <ji...@apache.org> on 2018/03/28 15:08:00 UTC

[jira] [Issue Comment Deleted] (IGNITE-6846) Add metrics for entry processor invocations

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

Alexey Kuznetsov updated IGNITE-6846:
-------------------------------------
    Comment: was deleted

(was: [~dpavlov] GridCacheNearAtomicMetricsSelfTest.testNearRead fails because of not related issue : atomic remove() operation doesn't remove entry from near cache. As a consequence, 'read' metric test fails.
So the problem isn't with metrics.)

> Add metrics for entry processor invocations
> -------------------------------------------
>
>                 Key: IGNITE-6846
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6846
>             Project: Ignite
>          Issue Type: Improvement
>          Components: cache
>    Affects Versions: 2.3
>            Reporter: Valentin Kulichenko
>            Assignee: Alexey Kuznetsov
>            Priority: Critical
>              Labels: iep-6
>             Fix For: 2.5
>
>
> {{CacheMetrics}} object has multiple metrics for various cache operations like {{get}}, {{put}} and {{remove}}, but nothing for {{invoke}}/{{EntryProcessor}}. It makes sense to add such metrics, for example:
> * Total number of `invoke` operations executed.
> * Number of `invoke` operations that included updates.
> * Number of read-only `invoke` operations.
> * Min/max/avg execution time.
> * ...



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