cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Radim Kolar (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-3741) OOMs because delete operations are not accounted
Date Fri, 13 Jan 2012 20:44:39 GMT

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

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

How can you OOM if you replace large inserts with small deletes?
                
> 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

        

Mime
View raw message