[
https://issues.apache.org/jira/browse/IGNITE-2483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-2483:
------------------------------------
Fix Version/s: (was: 2.0)
2.1
> Cache metrics functionality for client nodes should be developed.
> -----------------------------------------------------------------
>
> Key: IGNITE-2483
> URL: https://issues.apache.org/jira/browse/IGNITE-2483
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Reporter: Valentin Kulichenko
> Labels: community
> Fix For: 2.1
>
>
> User list discussion:
> http://apache-ignite-users.70518.x6.nabble.com/Is-there-a-way-to-get-cache-metrics-for-all-the-nodes-in-cluster-combined-td2674.html
> Currently there are at least three issues with cache metrics:
> # When metrics are acquired on client, average put times are always zero.
> This happens because timings are calculated on the client, but puts are
> counted on servers.
> # Size and keySize are always zero even if cache is not empty.
> # Default metrics() method that doesn't take a cluster group provides metrics
> for local node only. So if it's called on client, they are always empty. It
> should calculate metrics for the whole cluster instead.
> Also looks like this code is very undertested. Coverage should be
> significantly improved.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
