You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@crail.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/06/20 11:43:00 UTC
[jira] [Commented] (CRAIL-40) Start script does not work on
machines with <64G of memory
[ https://issues.apache.org/jira/browse/CRAIL-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16518062#comment-16518062 ]
ASF GitHub Bot commented on CRAIL-40:
-------------------------------------
GitHub user PepperJo opened a pull request:
https://github.com/apache/incubator-crail/pull/26
Start script: remove heap size argument
Remove Xmx and MaxDirectMemorySize argument from start script
since it does not allow to run Crail on machines with less
than 64G.
https://issues.apache.org/jira/browse/CRAIL-40
Signed-off-by: Jonas Pfefferle <pe...@apache.org>
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/PepperJo/incubator-crail start_script
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-crail/pull/26.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 #26
----
commit 7209748b399b8f6bcfbf4c87ff498dae3fd55e33
Author: Jonas Pfefferle <pe...@...>
Date: 2018-06-20T11:36:11Z
Start script: remove heap size argument
Remove Xmx and MaxDirectMemorySize argument from start script
since it does not allow to run Crail on machines with less
than 64G.
https://issues.apache.org/jira/browse/CRAIL-40
Signed-off-by: Jonas Pfefferle <pe...@apache.org>
----
> Start script does not work on machines with <64G of memory
> ----------------------------------------------------------
>
> Key: CRAIL-40
> URL: https://issues.apache.org/jira/browse/CRAIL-40
> Project: Apache Crail
> Issue Type: Bug
> Reporter: Jonas Pfefferle
> Priority: Major
>
> We set Xmx and MaxDirectMemorySize in the crail start script.
> We should remove them and come up with a better solution in how to configure heap size. I believe MaxDirectMemorySize is not needed at all, according to the documentation it just sets an limit otherwise it allows allocating as much direct memory as the size of the heap.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)