cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3741) OOMs because delete operations are not accounted
Date Thu, 03 May 2012 15:36:51 GMT


Jonathan Ellis commented on CASSANDRA-3741:

Thanks, Andriy.  You (and Vitalii) are right; whole-row deletions did indeed have zero throughput
because of that behavior.

Committed with a change to 12 bytes (long + int from deletion info) to match what we do with
Column sizes.  (We measure the serialized size in Memtable.currentThroughput, then multiply
by liveRatio to get a better estimate of the in-memory size.  Mixing internal overhead as
in CSLM would actually double count that.  I've also introduced CASSANDRA-4215 to clean this
up more for 1.2.
> OOMs because delete operations are not accounted
> ------------------------------------------------
>                 Key: CASSANDRA-3741
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.1.0
>         Environment: FreeBSD
>            Reporter: Vitalii Tymchyshyn
> Currently we are moving to new data format where new format is written into new CFs and
old one is deleted key-by-key. 
> I have started getting OOMs and found out that delete operations are not accounted and
so, column families are not flushed (changed == 0 with delete only operations) by storage
> This is pull request that fixed this problem for me:

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message