[
https://issues.apache.org/jira/browse/CASSANDRA-3741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13267506#comment-13267506
]
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: https://issues.apache.org/jira/browse/CASSANDRA-3741
> 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 manager.
> This is pull request that fixed this problem for me:
> https://github.com/apache/cassandra/pull/5
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
