[
https://issues.apache.org/jira/browse/CASSANDRA-3741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13458860#comment-13458860
]
Jonathan Ellis commented on CASSANDRA-3741:
-------------------------------------------
No, this is a sensitive area of the code and we don't want to risk
destabilizing it.
> 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
