[
https://issues.apache.org/jira/browse/CASSANDRA-11600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15247747#comment-15247747
]
Mike Lococo commented on CASSANDRA-11600:
-----------------------------------------
The code in question is this:
https://github.com/apache/cassandra/blob/a17120adffe6889ebbc4e76adb493898b6799a0d/conf/cassandra-env.sh#L145-L157
I believe the fix for any version of C* using G1 by default is simply to remove
the HEAP_NEWSIZE checks.
> Don't require HEAP_NEW_SIZE to be set when using G1
> ---------------------------------------------------
>
> Key: CASSANDRA-11600
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11600
> Project: Cassandra
> Issue Type: Bug
> Reporter: Blake Eggleston
> Assignee: Blake Eggleston
> Priority: Minor
> Fix For: 3.6, 3.0.x
>
>
> Although cassandra-env.sh doesn't set -Xmn (unless set in jvm.options) when
> using G1GC, it still requires that you set HEAP_NEW_SIZE and MAX_HEAP_SIZE
> together, and won't start until you do. Since we ignore that setting if
> you're using G1, we shouldn't require that the user set it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
