[
https://issues.apache.org/jira/browse/IGNITE-6846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16269747#comment-16269747
]
Valentin Kulichenko commented on IGNITE-6846:
---------------------------------------------
[~Alexey Kuznetsov], here are my comments.
1. Makes sense.
2. Metrics for total number of invocations should be incremented.
3. Correct.
4. This sounds like a weird case, how do you update multiple entries with one
entry processor invocation?
5. Correct. And this does not depend on what entry processor returns.
6. How does regular 'remove' metric behaves in this case? I think similar
'invoke' metric should be consistent with that one.
7. Can you draft the API and present it here?
> 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)
