cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Goffinet (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3675) ship with -XX:+ExplicitGCInvokesConcurrent by default
Date Tue, 07 Feb 2012 02:22:59 GMT


Chris Goffinet commented on CASSANDRA-3675:

For the record, I still think this is a sane default.
> ship with -XX:+ExplicitGCInvokesConcurrent by default
> -----------------------------------------------------
>                 Key: CASSANDRA-3675
>                 URL:
>             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:!default.jspa
For more information on JIRA, see:


View raw message