ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Goncharuk (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-5248) Best effort check to detect a 32-bit JVM trying to allocate too big amount of memory
Date Tue, 23 May 2017 08:37:04 GMT

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

Alexey Goncharuk commented on IGNITE-5248:
------------------------------------------

Thanks, for the contribution, Wuwei! I merged your patch with minor changes.

> Best effort check to detect a 32-bit JVM trying to allocate too big amount of memory
> ------------------------------------------------------------------------------------
>
>                 Key: IGNITE-5248
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5248
>             Project: Ignite
>          Issue Type: Improvement
>          Components: cache
>    Affects Versions: 2.0
>            Reporter: Alexey Goncharuk
>            Assignee: Wuwei Lin
>              Labels: important, newbie
>             Fix For: 2.1
>
>
> A follow-up on the user list discussion:
> http://apache-ignite-users.70518.x6.nabble.com/Ignite2-0-memory-policy-limit-td12840.html
> We can catch the IllegalArgumentException and see if the allocated space exceeds 2Gb.
In this case, we should suggest that user check that he is running a 64-bit JVM.



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

Mime
View raw message