[jira] [Commented] (CASSANDRA-3675) ship with -XX:+ExplicitGCInvokesConcurrent by default

["Jonathan Ellis (Commented) (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13201023#comment-13201023 ] 

Jonathan Ellis commented on CASSANDRA-3675:
-------------------------------------------

Of course the downside is that CMS is not compacting.  Given that fragmentation has been an issue I have reservations about changing this behavior from the default, expected behavior.  It seems to me that if people are in the "let's see what my working set is" testing phase, a STW collection is not going to cause big problems.
                
> 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
>         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