[
https://issues.apache.org/jira/browse/CASSANDRA-11600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15250757#comment-15250757
]
Blake Eggleston commented on CASSANDRA-11600:
---------------------------------------------
| *3.0* | *trunk* |
| [branch|https://github.com/bdeggleston/cassandra/tree/11600-3.0] |
[branch|https://github.com/bdeggleston/cassandra/tree/11600-trunk] |
|
[testall|http://cassci.datastax.com/view/Dev/view/bdeggleston/job/bdeggleston-11600-3.0-2-testall/1/]
|
[testall|http://cassci.datastax.com/view/Dev/view/bdeggleston/job/bdeggleston-11600-trunk-2-testall/1/]
|
|
[dtest|http://cassci.datastax.com/view/Dev/view/bdeggleston/job/bdeggleston-11600-3.0-2-dtest/1/]
|
[dtest|http://cassci.datastax.com/view/Dev/view/bdeggleston/job/bdeggleston-11600-trunk-2-dtest/1/]
|
commit info: should merge cleanly
> 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)
