+1 for G1 with such a heap size. And don't set heap new size, let g1 decide.
Inviato da Yahoo Mail su Android
Il mar, 20 set, 2016 alle 9:01, Jeff Jirsa ha scritto:
Major changes in 3.0, but the big ones involve storage - parent ticket is
https://issues.apache.org/jira/browse/CASSANDRA-942
Major changes in 3.0, but the big ones involve storage - parent ticket is
https://issues.apache.org/jira/browse/CASSANDRA-9427
64G cms heap with 4G new gen is somewhat atypical - would expect g1 at that
size, or at the very least a larger new gen to try to avoid promotion which
will bring you t
The way how hints work under the hood was improved in C* 3.0.
Please take a look at
http://www.datastax.com/dev/blog/whats-coming-to-cassandra-in-3-0-improved-hint-storage-and-delivery
for further details
On Tue, Sep 20, 2016 at 8:12 AM, Dikang Gu wrote:
> In our 2.1 cluster, I find that hints
In our 2.1 cluster, I find that hints handoff is using a lot of memory on
our proxy nodes, when delivering hints to a data node that was dead for 3+
hours (our hints window is 3 hours). It makes the young gen GC time as long
as 2 secs.
I'm using 64G max heap size, and 4G young gen size. I'm consid
