Return-Path: <commits-return-185058-archive-asf-public=cust-asf.ponee.io@cassandra.apache.org>
X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
	by cust-asf2.ponee.io (Postfix) with ESMTP id E8FCA200BB9
	for <archive-asf-public-internal@cust-asf2.ponee.io>; Mon,  7 Nov 2016 12:34:00 +0100 (CET)
Received: by cust-asf.ponee.io (Postfix)
	id E7BB5160AEB; Mon,  7 Nov 2016 11:34:00 +0000 (UTC)
Delivered-To: archive-asf-public@cust-asf.ponee.io
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by cust-asf.ponee.io (Postfix) with SMTP id 3A9DA160B11
	for <archive-asf-public@cust-asf.ponee.io>; Mon,  7 Nov 2016 12:34:00 +0100 (CET)
Received: (qmail 99258 invoked by uid 500); 7 Nov 2016 11:33:58 -0000
Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:commits-help@cassandra.apache.org>
List-Unsubscribe: <mailto:commits-unsubscribe@cassandra.apache.org>
List-Post: <mailto:commits@cassandra.apache.org>
List-Id: <commits.cassandra.apache.org>
Reply-To: dev@cassandra.apache.org
Delivered-To: mailing list commits@cassandra.apache.org
Received: (qmail 99028 invoked by uid 99); 7 Nov 2016 11:33:58 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Nov 2016 11:33:58 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id 91ED82C0D55
	for <commits@cassandra.apache.org>; Mon,  7 Nov 2016 11:33:58 +0000 (UTC)
Date: Mon, 7 Nov 2016 11:33:58 +0000 (UTC)
From: "nicolas ginder (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.13007530.1474887107000.208900.1478518438594@Atlassian.JIRA>
In-Reply-To: <JIRA.13007530.1474887107000@Atlassian.JIRA>
References: <JIRA.13007530.1474887107000@Atlassian.JIRA> <JIRA.13007530.1474887107892@arcas>
Subject: [jira] [Commented] (CASSANDRA-12707) JVM out of memory when
 querying an extra-large partition with lots of tombstones
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
archived-at: Mon, 07 Nov 2016 11:34:01 -0000


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

nicolas ginder commented on CASSANDRA-12707:
--------------------------------------------

C* 3.0 is not impacted as this part of the code was completely refactored. 

> JVM out of memory when querying an extra-large partition with lots of tombstones
> --------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-12707
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12707
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: nicolas ginder
>             Fix For: 2.1.x, 2.2.x
>
>
> We have an extra large partition of 40 million cells where most of the cells were deleted. When querying this partition with a slice query, Cassandra runs out of memory as tombstones fill up the JVM heap. After debugging one of the large SSTable we found that this part of the code loads all the tombstones.
> In org.apache.cassandra.db.filter.QueryFilter
> ...
> public static Iterator<Cell> gatherTombstones(final ColumnFamily returnCF, final Iterator<? extends OnDiskAtom> iter)
>     {
> ...
> while (iter.hasNext())
>                 {
>                     OnDiskAtom atom = iter.next();
>                     if (atom instanceof Cell)
>                     {
>                         next = (Cell)atom;
>                         break;
>                     }
>                     else
>                     {
>                         returnCF.addAtom(atom);
>                     }
>                 }
> ...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)