[
https://issues.apache.org/jira/browse/CASSANDRA-10403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15997986#comment-15997986
]
Spiros Ioannou commented on CASSANDRA-10403:
--------------------------------------------
Just a note here, even with 8G heap, some GC can take very long (8cpu machine,
2TB data size). While typical is about 220ms, it can take > 20sec.
WARN [Service Thread] 2017-05-02 10:44:08,772 GCInspector.java:282 -
ConcurrentMarkSweep GC in 20335ms. CMS Old Gen: 4251698688 -> 2490135992; Par
Eden Space: 671088640 -> 0; ...
That happens especially during repairs, and makes other nodes drop the one
doing the long GC, and makes almost all repairs fail. Using G1 seems a valid
option for production.
> 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: Configuration
> 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.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
