[
https://issues.apache.org/jira/browse/CASSANDRA-3741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13458932#comment-13458932
]
Radim Kolar commented on CASSANDRA-3741:
----------------------------------------
1.0 is already destabilized by this bug. If you want to have minimal effect,
then add just 1 byte to live bytes count for every delete. In non delete only
workload, it will have minimal effect.
Its important to have non zero count otherwise it will not be flushed to disk
on memory pressure.
> 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.0.0
> Environment: FreeBSD
> Reporter: Vitalii Tymchyshyn
> Assignee: Andriy Kolyadenko
> Fix For: 1.1.1
>
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
