[
https://issues.apache.org/jira/browse/CASSANDRA-3741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13186448#comment-13186448
]
Vitalii Tymchyshyn commented on CASSANDRA-3741:
-----------------------------------------------
Throughput size for deletion IS 0 for me. I am not deleting for some columns,
but all columns in a key and operation has 0 columns in this case, this means 0
throughput so I did introduce an overhead for memory operation storage that
looks good for me (20 bytes is ~ConcurrentMap size).
To note: I was getting OOM on startup/log replay.
The problem is that I have started delete-only workload from some Column
Families and this won't change as all inserts go into another column families:
we are moving. And for full-key delete-only throughput is 0
> 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
> 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
