Hello.
Thank you for answering the question.
Sorry, let me ask you another question.
In the same environment, set the replication factor to "4" again as follows.
Displayed the trace results of write and read operations at the consistency
level QUORUM.
> CREATE KEYSPACE test1 WITH REPLICATION =
Our experience with G1GC was that 31gb wasn’t optimal (for us) because while
you have less frequent full GCs they are bigger when they do happen. But even
so, not to the point of a 9.5s full collection.
Unless it is a rare event associated with something weird happening outside of
the JVM (the
Thanks everyone for the response.
How to debug more on GC issue ?
Is there any GC issue which is present in 3.11.0 ?
On Thu, Feb 27, 2020 at 8:46 AM Reid Pinchback
wrote:
> Our experience with G1GC was that 31gb wasn’t optimal (for us) because
> while you have less frequent full GCs they are big
I definitely saw a noticeable decrease in GC activity somewhere between
3.11.0 and 3.11.4. I'm not sure which change did it, but I can't think of
any good reason to use 3.11.0 vs 3.11.6.
I would enable and look through GC logs (or just the slow-GC entries in the
default log) to see if the problem
