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
underlying
problem.
From: "Steinmaurer, Thomas"
Reply-To: "user@cassandra.apache.org"
Date: Wednesday, November 6, 2019 at 11:27 AM
To: "user@cassandra.apache.org"
Subject: Cassandra 3.0.18 went OOM several hours after joining a cluster
Message from External Sender
He
Hello,
after moving from 2.1.18 to 3.0.18, we are facing OOM situations after several
hours a node has successfully joined a cluster (via auto-bootstrap).
I have created the following ticket trying to describe the situation, including
hprof / MAT screens: https://issues.apache.org/jira/browse/C
