[
https://issues.apache.org/jira/browse/CASSANDRA-10403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14957297#comment-14957297
]
Paulo Motta commented on CASSANDRA-10403:
-----------------------------------------
bq. Are we intending to drop jvm.options into /etc rather than /etc/cassandra?
That seems off to me.
That was a mistake during manual reconstruction of the nuked commit, the
correct is {{/etc/cassandra/jvm.options}}. Updated 10403 branch with correcton.
Sorry for the confusion!
During packaged install test, found that hints directory was not created
correctly so created CASSANDRA-10525 to address that. After fixing that,
switched from CMS to G1 on {{/etc/cassandra/jvm.options}} and then restarting
service reloaded options correctly, so seems to work well.
> Consider reverting to CMS GC on 3.0
> -----------------------------------
>
> Key: CASSANDRA-10403
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10403
> Project: Cassandra
> Issue Type: Improvement
> Components: Config
> Reporter: Joshua McKenzie
> Assignee: Paulo Motta
> Fix For: 3.0.0 rc2
>
>
> Reference discussion on CASSANDRA-7486.
> For smaller heap sizes G1 appears to have some throughput/latency issues when
> compared to CMS. With our default max heap size at 8G on 3.0, there's a
> strong argument to be made for having CMS as the default for the 3.0 release.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
