[IGNITE-3495] CacheMetrics.getAverage###Time is not calculated properly

• Type: Bug
• Status: Reopened
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.6
• Fix Version/s: 3.0
• Labels: IEP-35 iep-6
• Assignee: Nikita Amelchev
• Reporter: Denis A. Magda
• Created: 18/Jul/16 11:45
• Updated: 26/Dec/19 12:41

Description

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.

Issue Links

• is duplicated by: IGNITE-6966 Average time metrics are not calculated for client driven operations
• is duplicated by: IGNITE-2636 Server cache metrics for put-get-remove avg time are incorrect for case when request sent from client
• is duplicated by: IGNITE-6420 Time metrics (CacheMetrics.getAverage###Time) should be calculated on primary node in case of ATOMIC cache
• is related to: IGNITE-12453 Cache operations metrics on affinity nodes