Some environment details like Cassandra version, amount of physical RAM,
JVM configs (heap and others), and any other non-default cassandra.yaaml
configs would help. The amount of data, number of keyspaces & tables,
since you mention "clients", would also be helpful for people to suggest
tuning improvements.
Michael
On 1/24/20 5:16 AM, Behroz Sikander wrote:
We recently had a lot of OOM in C* and it was generally happening during
startup.
We took some heap dumps but still cannot pin point the exact reason. So, we
need some help from experts.
Our clients are not explicitly deleting data but they have TTL enabled.
C* details:
show version
[cqlsh 5.0.1 | Cassandra 2.2.9 | CQL spec 3.3.1 | Native protocol v4]
Most of the heap was allocated was the object[]
- org.apache.cassandra.db.Cell
Heap dump images:
Heap usage by class: https://pasteboard.co/IRrfu70.png
Classes using most heap: https://pasteboard.co/IRrgszZ.png
Overall heap usage: https://pasteboard.co/IRrg7t1.png
What could be the reason for such OOM? Something that we can tune to improve
this?
Any help would be much appreciated.
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org
