You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Mikhail Cherkasov (JIRA)" <ji...@apache.org> on 2018/03/26 21:35:00 UTC
[jira] [Commented] (IGNITE-5583) Switch non-heap memory metrics to
new page memory semantics
[ https://issues.apache.org/jira/browse/IGNITE-5583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16414595#comment-16414595 ]
Mikhail Cherkasov commented on IGNITE-5583:
-------------------------------------------
I changed the ticket type from improvement to bug, lines like:
^-- Non heap [used=74MB, free=95.11%, comm=77MB]
are misleading for users, everyone expects to see off memory here.
Who does need jvm non-heap size at all?
> 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: Bug
> 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
(v7.6.3#76005)