Hi Aaron,
Thanks for reply. I did some more tests and it looks like the problem is
not in deletes/writes, it rather in reads (I do read before deleting).
It turns out that problem was in another CF which had wide row of 1.2GB
and row cache. Cassandra tries to read this row into cache and beco
Delete is a no look write operation, like normal writes. So it should not be
directly causing a lot of memory allocation.
It may be causing a lot of compaction activity, which due to the wide row may
be throwing up lots of GC.
Try the following to get through the deletions:
* disable compact
