ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Kuznetsov (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (IGNITE-6846) Add metrics for entry processor invocations
Date Thu, 30 Nov 2017 12:22:00 GMT

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

Alexey Kuznetsov edited comment on IGNITE-6846 at 11/30/17 12:21 PM:
---------------------------------------------------------------------

[~vkulichenko] Ok, Im going to rework API.
And make 'invoke' metrics be calculated the similar way as corresponding regular cache operations.
There will be problems with implementing "getAverageEntryProcessorReadOnlyInvocationTime();"
metric, because we don't know whether invoke is read-only or not on initiating node(node,
initiated invoke operation, and waiting for invoke response from cluster)


was (Author: alexey kuznetsov):
[~vkulichenko] Ok, Im going to rework API.
And make 'invoke' metrics be calculated the similar way as corresponding regular cache operations.
There will be problems with implementing "getAverageEntryProcessorReadOnlyInvocationTime();"
metric, because we don't know whether invoke is read-only or not on initiating node(node,
initiated invoke operation, and waiting for invoke response from cluster)

But again. Currently for regular remove operation(in case if cache is empty):
* In TRANSACTIONAL cache 'remove' metric is incremented on nodes
* But, in ATOMIC cache its not incremented.
Seems its a bug?

> 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.4
>
>
> {{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
(v6.4.14#64029)

Mime
View raw message