[
https://issues.apache.org/jira/browse/IGNITE-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15358842#comment-15358842
]
Denis Magda commented on IGNITE-3409:
-------------------------------------
Vladimir, this has been fixed long time ago.
ignite.sh contains the following check
{code}
if [ -z "$JVM_OPTS" ] ; then
if [[ `"$JAVA" -version 2>&1 | egrep "1\.[7]\."` ]]; then
JVM_OPTS="-Xms1g -Xmx1g -server -XX:+AggressiveOpts
-XX:MaxPermSize=256m"
else
JVM_OPTS="-Xms1g -Xmx1g -server -XX:+AggressiveOpts
-XX:MaxMetaspaceSize=256m"
fi
fi
{code}
while ignite.bat this one
{code}
"%JAVA_HOME%\bin\java.exe" -version 2>&1 | findstr "1\.[7]\." > nul
if %ERRORLEVEL% equ 0 (
if "%JVM_OPTS%" == "" set JVM_OPTS=-Xms1g -Xmx1g -server
-XX:+AggressiveOpts -XX:MaxPermSize=256m
) else (
if "%JVM_OPTS%" == "" set JVM_OPTS=-Xms1g -Xmx1g -server
-XX:+AggressiveOpts -XX:MaxMetaspaceSize=256m
)
{code}
Doesn't this work on your side?
> Improve permgen/metaspace settings.
> -----------------------------------
>
> Key: IGNITE-3409
> URL: https://issues.apache.org/jira/browse/IGNITE-3409
> Project: Ignite
> Issue Type: Task
> Components: general
> Affects Versions: 1.6
> Reporter: Vladimir Ozerov
> Priority: Critical
> Fix For: 1.7
>
>
> Currently we explicitly set {{MaxPermSize}} in several places. Most notable -
> {{ignite.bat}} and {{ignite.sh}}.
> As most users are on Java 8 now, they see annoying JVM warning on node
> startup:
> {quote}OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
> support was removed in 8.0{quote}
> Let update our scripts, so that {{MaxPermSize}} is used for Java 7 and
> {{MaxMetaspaceSize}} for Java 8 +.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
