In fact I truncated hints table to stabilize the cluster. Through the heap
dumps I was able to identify the table on which there were numerous queries.
Then I focused on system_traces.session table around the time OOM occurred. It
turned out to be a full table scan on a large table which caused
I was looking at nodetool info across all nodes. Consistently JVM heap used is
~ 12GB and off heap is ~ 4-5GB.
From: Thakrar, Jayesh
Sent: Saturday, March 4, 2017 9:23:01 AM
To: Shravan C; Joaquin Casares; user@cassandra.apache.org
Subject: Re: OOM on Apache
We run C* at 32 GB and all servers have 96GB RAM. We use STCS . LCS is not an
option for us as we have frequent updates.
Thanks,
Shravan
From: Thakrar, Jayesh
Sent: Friday, March 3, 2017 3:47:27 PM
To: Joaquin Casares; user@cassandra.apache.org
Subject: Re: OOM
Hi Joaquin,
We have inserts going into a tracking table. Tracking table is a simple table
[PRIMARY KEY (comid, status_timestamp) ] with a few tracking attributes and
sorted by status_timestamp. From a volume perspective it is not a whole lot.
Thanks,
Shravan
F
