You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/05/25 12:34:04 UTC
[jira] [Commented] (IGNITE-5288) Inconsistency of committed and the
max memory numbers should not cause stopping node
[ https://issues.apache.org/jira/browse/IGNITE-5288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16024667#comment-16024667 ]
ASF GitHub Bot commented on IGNITE-5288:
----------------------------------------
GitHub user dspavlov opened a pull request:
https://github.com/apache/ignite/pull/2006
IGNITE-5288: Inconsistency of committed and the max memory numbers …
…should not cause stopping cluster node
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5288
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/2006.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2006
----
commit 0fc8c4531a86a6f13a1387a0757d3ecbd5da1e36
Author: dpavlov <dp...@gridgain.com>
Date: 2017-05-25T12:31:00Z
IGNITE-5288: Inconsistency of committed and the max memory numbers should not cause stopping cluster node
----
> 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
>
> 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)