ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-5288) Inconsistency of committed and the max memory numbers should not cause stopping node
Date Thu, 01 Jun 2017 09:28:04 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-5288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032691#comment-16032691
] 

ASF GitHub Bot commented on IGNITE-5288:
----------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/ignite/pull/2006


> Inconsistency of committed and the max memory numbers should not cause stopping node
> ------------------------------------------------------------------------------------
>
>                 Key: IGNITE-5288
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5288
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Dmitriy Pavlov
>            Assignee: Dmitriy Pavlov
>             Fix For: 2.1
>
>
> http://apache-ignite-users.70518.x6.nabble.com/Ignite-and-Memory-Info-td13111.html
> When using Ignite 1.7 together with Excelsior JET Ahead-Of-Time Compiler we get this
error on various occasions:
>  
> {noformat}
> java.lang.IllegalArgumentException: committed = 5274103808 should be < max = 5274095616
>     	at java.lang.management.MemoryUsage.<init>(Unknown Source)
>     	at sun.management.MemoryImpl.<unknown>(Unknown Source)
>     	at sun.management.MemoryImpl.getHeapMemoryUsage(Unknown Source)
>     	at org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$6.getHeapMemoryCommitted(GridDiscoveryManager.java:778)
>     	at org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$7.metrics(GridDiscoveryManager.java:878)
>     	at org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processHeartbeatMessage(ServerImpl.java:4651)
>     	at org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2325)
>     	at org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2135)
>     	at org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.body(ServerImpl.java:6123)
>     	at org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.body(ServerImpl.java:2222)
>     	at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> {noformat}
> The committed and the max memory numbers are not consistent and getHeapMemoryUsage()
throws a IllegalArgumentEx about it.
>  
>  GridDiscoveryManager can get such error and not kill the whole process because of it.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message