[
https://issues.apache.org/jira/browse/IGNITE-15666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17447530#comment-17447530
]
Amelchev Nikita edited comment on IGNITE-15666 at 11/22/21, 5:12 PM:
---------------------------------------------------------------------
[~slava.koptilin], I think this metric should not be used to calculate the
average time. We can have several backups, unstable topology, network delays
etc that will lead to a wrong value. (in addition, batch remove time also count
missed removals but by the JCache API specification should not)
I think we should implement a correct time metric for that purpose.
was (Author: nsamelchev):
[~slava.koptilin], I think this metric should not be used to calculate the
average time. We can have several backups, unstable topology, clients reconnect
etc that will lead to a wrong value. (in addition, batch remove time also count
missed removals but by the JCache API specification should not)
I think we should implement a correct time metric for that purpose.
> 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)
