Hello,
If your problem is in the read path, there are things you can check to see
what's wrong along the way:
- 'nodetool tablestats' (look at the more important tables first - biggest
volume/throughput). A lot of information at the table level, very useful to
troubleshoot. If you have any questi
Thanks for the recommendation Jeff, I'll try to get a heap dump next time
this happens and try the other changes in the mean time.
Also not sure but this CASSANDRA-13900 looked it might be related.
On Sat, Jun 30, 2018 at 9:51 PM, Jeff Jirsa wrote:
> The young gcs loom suspicious
>
> Without se
The young gcs loom suspicious
Without seeing the heap it’s hard to be sure, but be sure you’re adjusting your
memtable (size and flush threshold), and you may find moving it offheap helps
too
Beyond that, debugging usually takes a heap dump and inspection with yourkit or
MAT or similar
3.0.14
