[
https://issues.apache.org/jira/browse/IGNITE-13404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Darlington updated IGNITE-13404:
----------------------------------------
Description:
ignite.sh [tries to set parameters for the
JVM|https://github.com/apache/ignite/blob/master/bin/ignite.sh#L102] if they've
not been set by the user (defaulting to 1Gb heap), unfortunately, it's always
set by an earlier part of the startup scripts.
Conversely, ignitevisorcmd.sh always sets the same parameters, even if they
have already been set by the user.
was:ignite.sh [tries to set parameters for the
JVM|https://github.com/apache/ignite/blob/master/bin/ignite.sh#L102] if they've
not been set by the user (defaulting to 1Gb heap), unfortunately it's always
set by an earlier part of the startup scripts.
> ignite.sh fails to set default JVM parameters
> ---------------------------------------------
>
> Key: IGNITE-13404
> URL: https://issues.apache.org/jira/browse/IGNITE-13404
> Project: Ignite
> Issue Type: Bug
> Environment: Anything but Windows.
> Reporter: Stephen Darlington
> Assignee: Stephen Darlington
> Priority: Minor
>
> ignite.sh [tries to set parameters for the
> JVM|https://github.com/apache/ignite/blob/master/bin/ignite.sh#L102] if
> they've not been set by the user (defaulting to 1Gb heap), unfortunately,
> it's always set by an earlier part of the startup scripts.
> Conversely, ignitevisorcmd.sh always sets the same parameters, even if they
> have already been set by the user.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
