[
https://issues.apache.org/jira/browse/IGNITE-6846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16264488#comment-16264488
]
Alexey Kuznetsov edited comment on IGNITE-6846 at 11/24/17 2:41 PM:
--------------------------------------------------------------------
When entry is updated, both 'invoke update' and get\put\remove metrics updated.
When entry processor is invoked, but cache entry isn't affected, then invoke
metric isn't incremented.
'invoke update' metrics incremented only when cache entry value is changed(or
removed) by entry processor(not just when entry processor is invoked).
If entry processor process(...) is called once, and multiple entries(perhaps on
different nodes) are affected, then local invoke metric is incremented only
once, cluster global metric is incremented once.
Read-only 'invoke' operation is processor invocation without calling
entry.setValue(...), processor still can return nin-null value.
was (Author: alexey kuznetsov):
when entry is updated, both 'invoke update' and get\put\remove metrics updated.
when entry processor is invoked, but cache entry isn't affected, then invoke
metric isn't incremented.
'invoke * ' metrics incremented only when cache entry value is affected(read or
updated) by entry processor(not just when entry processor is invoked).If entry
processor is called once, and multiple entries(on different nodes) are
affected, then local invoke metric is incremented only once, cluster global
metric is incremented once.
> 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)
