[
https://issues.apache.org/jira/browse/IGNITE-5248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16018346#comment-16018346
]
ASF GitHub Bot commented on IGNITE-5248:
----------------------------------------
GitHub user vinx13 opened a pull request:
https://github.com/apache/ignite/pull/1976
IGNITE-5248: Detect a 32-bit JVM using too large init page size
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vinx13/ignite ignite-5248
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/1976.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 #1976
----
commit f797eb6a2d18275877fd36574ec4477f0b4d14b5
Author: Wuwei Lin <[email protected]>
Date: 2017-05-20T06:38:19Z
IGNITE-5248: Detect a 32-bit JVM trying to allocate too big amount of
memory in memory policy
----
> 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: 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)
