We have (have had for some time) abnormally wide partitions in Cassandra. These are the source of a number of problems, not least of which are fatally large heap allocations that result in OOMs when read.
We should a) find those that currently exist and clean them up, and b) put in place the means to proactively identify them moving forward.
|18||Partitions larger than 10G in size|
|30||> 5G and <= 10G in size|
|653||> 1G and <= 5G in size|
(raw log entries)