ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladislav Pyatkov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-3495) CacheMetrics.getAverage###Time is not calculated properly
Date Wed, 20 Jul 2016 08:45:21 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15385554#comment-15385554

Vladislav Pyatkov commented on IGNITE-3495:

[~agoncharuk] I think, duration is the execution time of the method (Not time consume to access
to data).
The functionality is not new for Ignite. You can see how to do it in (cache.GridCacheAdapter#put()).

> CacheMetrics.getAverage###Time is not calculated properly
> ---------------------------------------------------------
>                 Key: IGNITE-3495
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3495
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Denis Magda
>            Assignee: Vladislav Pyatkov
>         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}}
> - start {{ExampleNodeStartupClient}}. You will see that average metrics are not incremented.

This message was sent by Atlassian JIRA

View raw message