Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
Date: Thu, 28 Jan 2016 03:54:39 +0000 (UTC)
From: "Valentin Kulichenko (JIRA)" <jira@apache.org>
To: issues@ignite.apache.org
Message-ID: <JIRA.12934677.1453953254000.232505.1453953279850@Atlassian.JIRA>
In-Reply-To: <JIRA.12934677.1453953254000@Atlassian.JIRA>
References: <JIRA.12934677.1453953254000@Atlassian.JIRA>
 <JIRA.12934677.1453953254926@arcas>
Subject: [jira] [Created] (IGNITE-2483) Cache metrics bugs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Valentin Kulichenko created IGNITE-2483:
-------------------------------------------

             Summary: Cache metrics bugs
                 Key: IGNITE-2483
                 URL: https://issues.apache.org/jira/browse/IGNITE-2483
             Project: Ignite
          Issue Type: Bug
          Components: cache
            Reporter: Valentin Kulichenko
             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)