[IGNITE-5288] Inconsistency of committed and the max memory numbers should not cause stopping node

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.1
• Assignee: Dmitry Pavlov
• Reporter: Dmitry Pavlov
• Created: 24/May/17 17:30
• Updated: 15/Sep/17 11:00
• Resolved: 01/Jun/17 09:28

Description

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:

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.

Issue Links

• is duplicated by: IGNITE-6062 IllegalArgumentException thrown while getHeapMemoryUsage()
• links to: GitHub Pull Request #2006