Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9974CD219 for ; Wed, 19 Sep 2012 17:09:09 +0000 (UTC) Received: (qmail 59475 invoked by uid 500); 19 Sep 2012 17:09:09 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 59445 invoked by uid 500); 19 Sep 2012 17:09:09 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 59379 invoked by uid 99); 19 Sep 2012 17:09:09 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Sep 2012 17:09:09 +0000 Date: Thu, 20 Sep 2012 04:09:09 +1100 (NCT) From: "Jonathan Ellis (JIRA)" To: commits@cassandra.apache.org Message-ID: <631255529.98093.1348074549286.JavaMail.jiratomcat@arcas> In-Reply-To: <1129524022.37697.1326458079664.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (CASSANDRA-3741) OOMs because delete operations are not accounted MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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