[jira] [Updated] (IGNITE-2483) Cache metrics functionality for client nodes should be developed.
[ https://issues.apache.org/jira/browse/IGNITE-2483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-2483: Labels: community iep-6 (was: community) > 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 >Priority: Major > Labels: community, iep-6 > > 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 (v7.6.3#76005)
[jira] [Updated] (IGNITE-2483) Cache metrics functionality for client nodes should be developed.
[ 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)
[jira] [Updated] (IGNITE-2483) Cache metrics functionality for client nodes should be developed.
[ 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: 1.8) 2.0 > 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.0 > > > 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.4#6332)
[jira] [Updated] (IGNITE-2483) Cache metrics functionality for client nodes should be developed.
[ https://issues.apache.org/jira/browse/IGNITE-2483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-2483: - Assignee: (was: Alexey Goncharuk) > 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: 1.8 > > > 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.4#6332)
[jira] [Updated] (IGNITE-2483) Cache metrics functionality for client nodes should be developed.
[ https://issues.apache.org/jira/browse/IGNITE-2483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-2483: --- Fix Version/s: (was: 1.7) 1.8 > 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 >Assignee: Alexey Goncharuk > Labels: community > Fix For: 1.8 > > > 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.4#6332)
[jira] [Updated] (IGNITE-2483) Cache metrics functionality for client nodes should be developed.
[ https://issues.apache.org/jira/browse/IGNITE-2483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-2483: Fix Version/s: (was: 1.6) 1.7 > 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 >Assignee: Alexey Goncharuk > Labels: community > Fix For: 1.7 > > > 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.4#6332)
[jira] [Updated] (IGNITE-2483) Cache metrics functionality for client nodes should be developed.
[ https://issues.apache.org/jira/browse/IGNITE-2483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ershov updated IGNITE-2483: Summary: Cache metrics functionality for client nodes should be developed. (was: Cache metrics bugs) > 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 >Assignee: Vladimir Ershov > Labels: community > Fix For: 1.6 > > > 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.4#6332)
