ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitriy Pavlov (JIRA)" <j...@apache.org>
Subject [jira] [Created] (IGNITE-5288) Inconsistency of committed and the max memory numbers should not cause stopping cluster
Date Wed, 24 May 2017 17:30:04 GMT
Dmitriy Pavlov created IGNITE-5288:
--------------------------------------

             Summary: Inconsistency of committed and the max memory numbers should not cause
stopping cluster
                 Key: IGNITE-5288
                 URL: https://issues.apache.org/jira/browse/IGNITE-5288
             Project: Ignite
          Issue Type: Improvement
            Reporter: Dmitriy Pavlov
            Assignee: Dmitriy Pavlov


When using Ignite 1.7 together with Excelsior JET Ahead-Of-Time Compiler we get this error
on various occasions:
 
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)
 
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