[
https://issues.apache.org/jira/browse/IGNITE-15666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17447519#comment-17447519
]
Vyacheslav Koptilin edited comment on IGNITE-15666 at 11/22/21, 4:34 PM:
-------------------------------------------------------------------------
Hello [~NSAmelchev],
Let's consider the following simple scenario: we have only one server node
which is an affinity node and initiator as well. In that case, both metrics
will be calculated on that server node. And so, metrics value will be broken, I
think.
Moreover, if you have a cluster you can aggregate these metrics across all
nodes, and therefore, it is possible to calculate the number of _removals_ and
_averageTime_ (see _ClusterGroup#metrics()_)
was (Author: slava.koptilin):
Hello [~NSAmelchev],
Let's consider the following simple scenario: we have only one server node
which is an affinity node and initiator as well. In that case, both metrics
will be calculated on that server node. And so, metrics value will be broken, I
think.
Moreover, if you have a cluster you can aggregate these metrics across all
nodes, and therefore, it is possible to calculate the number of _removals_ and
_averageTime_.
> 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)
