You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Radim Kolar (JIRA)" <ji...@apache.org> on 2012/09/19 18:57:08 UTC

[jira] [Commented] (CASSANDRA-3741) OOMs because delete operations are not accounted

    [ https://issues.apache.org/jira/browse/CASSANDRA-3741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13458849#comment-13458849 ] 

Radim Kolar commented on CASSANDRA-3741:
----------------------------------------

was this backported to cassandra 1.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.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