aurer, Thomas"
Reply-To: "user@cassandra.apache.org"
Date: Wednesday, November 6, 2019 at 2:43 PM
To: "user@cassandra.apache.org"
Subject: RE: Cassandra 3.0.18 went OOM several hours after joining a cluster
Message from External Sender
Reid,
thanks for thoughts.
I agree
t;user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>
Subject: Re: Cassandra 3.0.18 went OOM several hours after joining a cluster
Message from External Sender
My first thought was that you were running into the merkle tree depth problem,
but t
of them, until eventually…pop.
From: Reid Pinchback
Reply-To: "user@cassandra.apache.org"
Date: Wednesday, November 6, 2019 at 12:11 PM
To: "user@cassandra.apache.org"
Subject: Re: Cassandra 3.0.18 went OOM several hours after joining a cluster
Message from External Sender
My
My first thought was that you were running into the merkle tree depth problem,
but the details on the ticket don’t seem to confirm that.
It does look like eden is too small. C* lives in Java’s GC pain point, a lot
of medium-lifetime objects. If you haven’t already done so, you’ll want to
con
