ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Ershov (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (IGNITE-2483) Cache metrics functionality for client nodes should be developed.
Date Tue, 16 Feb 2016 16:14:18 GMT

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

Vladimir Ershov reassigned IGNITE-2483:
---------------------------------------

    Assignee: Alexey Goncharuk  (was: Vladimir Ershov)

> 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.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)

Mime
View raw message