cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Blake Eggleston (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Deleted] (CASSANDRA-11600) Don't require HEAP_NEW_SIZE to be set when using G1
Date Wed, 20 Apr 2016 21:35:25 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-11600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Blake Eggleston updated CASSANDRA-11600:
----------------------------------------
    Comment: was deleted

(was: patches:
[3.0|https://github.com/bdeggleston/cassandra/tree/11600-3.0]
[trunk|https://github.com/bdeggleston/cassandra/tree/11600-trunk])

> 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)

Mime
View raw message