[
https://issues.apache.org/jira/browse/IGNITE-6846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16417786#comment-16417786
]
Dmitriy Pavlov commented on IGNITE-6846:
----------------------------------------
In reply to
Dmitriy Pavlov 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.
So, it seems it is really separate issue. I'm ok with merge and mute added test
with separate ticket.
See also
http://apache-ignite-developers.2346864.n4.nabble.com/Near-cache-entry-removal-td28698.html
> 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)
