You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Tupitsyn (JIRA)" <ji...@apache.org> on 2017/05/30 15:16:04 UTC
[jira] [Comment Edited] (IGNITE-5124) MemoryMetrics API
Improvements
[ https://issues.apache.org/jira/browse/IGNITE-5124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16029534#comment-16029534 ]
Pavel Tupitsyn edited comment on IGNITE-5124 at 5/30/17 3:15 PM:
-----------------------------------------------------------------
[~agoncharuk] [~sergey-chugunov] I see that {{rateTimeInterval}} is {{int}} and in seconds, which is inconsistent with all other configuration properties in Ignite (which are {{long}} and in milliseconds). Can we fix that?
was (Author: ptupitsyn):
[~agoncharuk] [~sergey-chugunov] I see that {{rateTimeInterval}} is in seconds, which is inconsistent with all other configuration properties in Ignite (which are {{long}} and in milliseconds). Can we fix that?
> MemoryMetrics API Improvements
> ------------------------------
>
> Key: IGNITE-5124
> URL: https://issues.apache.org/jira/browse/IGNITE-5124
> Project: Ignite
> Issue Type: Task
> Components: general
> Reporter: Denis Magda
> Assignee: Sergey Chugunov
> Labels: important
> Fix For: 2.1
>
>
> * Ignite.memoryMetrics() returns a collection of metrics. However, it’s unclear what exactly the collection includes. Is every element of the collection is a latest snapshot of a specific memory region defined by memory policy and the the total size of the collection is equal to the total number of such regions configured on a node? This has to be clarified in java doc before 2.0 release.
> * I would have Ignite.memoryMetrics(name) methods that will return the metrics for a concrete region configured by memory policy. It’s fine to add the method under 2.1 (create a ticket).
> * I would add “setRateInterval” and “setSubIntervals” methods to MemoryPolicyConfiguration because now I have to get a JMX bean if to want to change the parameter. Again, feel free do this under 2.0 or move to 2.1 if there is no time for that.
> Original discussion: http://apache-ignite-developers.2346864.n4.nabble.com/MemoryMetrics-interface-inconsistencies-td17156.html
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)