[
https://issues.apache.org/jira/browse/CASSANDRA-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13201025#comment-13201025
]
Peter Schuller commented on CASSANDRA-3675:
-------------------------------------------
Btw I have been in a position several times of a production cluster having some
kind of issue, and wanting to know what the live set is in a situation where I
don't want to trigger full gcs. It's also a way to trigger CMS earlier without
having to restart a node (temporarily).
> ship with -XX:+ExplicitGCInvokesConcurrent by default
> -----------------------------------------------------
>
> Key: CASSANDRA-3675
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3675
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Peter Schuller
> Assignee: Peter Schuller
> Priority: Minor
> Fix For: 1.1
>
> Attachments: CASSANDRA-3675-trunk.txt
>
>
> It's so much easier if you can safely tell people to trigger a full GC to
> discover their live set (see CASSANDRA-3574), instead of explaining the
> behavior of CMS and what the memory usage graph looks like etc etc. Shipping
> with {{-XX:+ExplicitGCInvokesConcurrent}} means this is by default safe.
> For people that have special needs like some kind of rolling compacting GC
> with disablegossip, they are special enough that they can just change the VM
> options.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
