[jira] [Resolved] (IGNITE-3495) CacheMetrics.getAverage###Time is not calculated properly

["Maxim Muzafarov (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IGNITE-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maxim Muzafarov resolved IGNITE-3495.
-------------------------------------
    Resolution: Won't Fix

The issue is not actual any more and will be covered under IEP-35 activities.

https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=112820392

> CacheMetrics.getAverage###Time is not calculated properly
> ---------------------------------------------------------
>
>                 Key: IGNITE-3495
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3495
>             Project: Ignite
>          Issue Type: Bug
>    Affects Versions: 1.6
>            Reporter: Denis A. Magda
>            Priority: Major
>              Labels: iep-6
>             Fix For: 2.8
>
>         Attachments: ExampleNodeStartupClient.java, IGNITE_3495.patch, example-default.xml
>
>
> {{CacheMetrics.getAverageGetTime}}, {{CacheMetrics.getAveragePutTime}} and {{CacheMetrics.getAverageRemoveTime}} are not calculated properly in the following scenario:
> - start a server node;
> - start a client node that will perform gets and puts;
> - {{CacheMetrics.getAverage###Time}} will always be 0 for the server node's cluster group.
> The issue happens because {{CacheMetricsImpl.add###TimeNanos}} method is not called on the server side when a metric related event happens.
> In the attache you can find source that showcases the bug.
> - start basic {{ExampleNodeStartup}} using attached configuration {{example-default.xml}} conjuration;
> - start {{ExampleNodeStartupClient}}. You will see that average metrics are not incremented.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)