[
https://issues.apache.org/jira/browse/IGNITE-15666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17449141#comment-17449141
]
Ivan Daschinsky commented on IGNITE-15666:
------------------------------------------
>> Why you are talking about getAverageMissTime()? (This method does not exist
>> and does not relate to the discussion, I think).
Yep, it doesn't exist. No, it does relate to discussion.
>> The spec defines only statistics.
The mentioned paragraph is not about statistics per se, it is about counters
(integer numbers)
>> that this behavior is logically correct?
Yes, it is logically correct. We should track both success and failures. And
spec is about the same. There are
many counters, but only 3 average time gauges.
As for me, totalRemovedTime metrics is useless, but let it be.
> The remove metric value is different for sync and async methods
> ---------------------------------------------------------------
>
> Key: IGNITE-15666
> URL: https://issues.apache.org/jira/browse/IGNITE-15666
> Project: Ignite
> Issue Type: Bug
> Reporter: Amelchev Nikita
> Assignee: Amelchev Nikita
> Priority: Major
> Fix For: 2.12
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The remove metric value is different for sync and async methods.
> The following metrics are updated only if the key was exist for the sync
> version:
> {noformat}
> RemoveTimeTotal
> RemoveTime
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
