ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitriy Pavlov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-5583) Switch non-heap memory metrics to new page memory semantics
Date Fri, 23 Jun 2017 18:12:01 GMT

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

Dmitriy Pavlov updated IGNITE-5583:
-----------------------------------
    Description: 
On jdk 1.8.0_131 there is negative amount of maximum non heap memory returned by following
code:
ManagementFactory.getMemoryMXBean().getNonHeapMemoryUsage().getMax());
returns -1.
 
And this value is used in ignite metrics in GridLocalMetrics.getNonHeapMemoryMaximum() which
becomes negative.

It is required to switch non-heap memory metrics to new page memory semantics, this should
show a clean picture in the node output and will also protect us from ambiguous -1 output.

See also discussion here: http://apache-ignite-developers.2346864.n4.nabble.com/Negative-non-heap-memory-maximum-td17990.html


  was:
On jdk 1.8.0_131 there is negative amount of maximum non heap memory returned by following
code:
ManagementFactory.getMemoryMXBean().getNonHeapMemoryUsage().getMax());
returns -1.
 
And this value is used in ignite metrics in GridLocalMetrics.getNonHeapMemoryMaximum() which
becomes negative.

It is required to switch non-heap memory metrics to new page memory
semantics, this should show a clean picture in the node output and will
also protect us from ambiguous -1 output.



> Switch non-heap memory metrics to new page memory semantics
> -----------------------------------------------------------
>
>                 Key: IGNITE-5583
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5583
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Dmitriy Pavlov
>            Assignee: Dmitriy Pavlov
>            Priority: Minor
>
> On jdk 1.8.0_131 there is negative amount of maximum non heap memory returned by following
code:
> ManagementFactory.getMemoryMXBean().getNonHeapMemoryUsage().getMax());
> returns -1.
>  
> And this value is used in ignite metrics in GridLocalMetrics.getNonHeapMemoryMaximum()
which becomes negative.
> It is required to switch non-heap memory metrics to new page memory semantics, this should
show a clean picture in the node output and will also protect us from ambiguous -1 output.
> See also discussion here: http://apache-ignite-developers.2346864.n4.nabble.com/Negative-non-heap-memory-maximum-td17990.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message