ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Ozerov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-3495) CacheMetrics.getAverage###Time is not calculated properly
Date Mon, 10 Apr 2017 12:22:41 GMT

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

Vladimir Ozerov updated IGNITE-3495:
------------------------------------
    Fix Version/s:     (was: 2.0)
                   2.1

> 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.1
>
>         Attachments: example-default.xml, ExampleNodeStartupClient.java, IGNITE_3495.patch
>
>
> {{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.15#6346)

Mime
View raw message