You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Denis Magda (JIRA)" <ji...@apache.org> on 2016/08/02 16:08:20 UTC

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

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

Denis Magda updated IGNITE-3495:
--------------------------------
    Fix Version/s: 2.0

> 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 Magda
>            Assignee: Vladislav Pyatkov
>             Fix For: 2.0
>
>         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
(v6.3.4#6332)