Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 83435 invoked from network); 8 Apr 2010 16:09:31 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 8 Apr 2010 16:09:31 -0000 Received: (qmail 18323 invoked by uid 500); 8 Apr 2010 16:09:30 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 18302 invoked by uid 500); 8 Apr 2010 16:09:30 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 18294 invoked by uid 99); 8 Apr 2010 16:09:30 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Apr 2010 16:09:30 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of tsaloranta@gmail.com designates 209.85.160.44 as permitted sender) Received: from [209.85.160.44] (HELO mail-pw0-f44.google.com) (209.85.160.44) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Apr 2010 16:09:23 +0000 Received: by pwj2 with SMTP id 2so2050106pwj.31 for ; Thu, 08 Apr 2010 09:09:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:content-type; bh=VD5woOWI4LVM+kbnK4o8urGfKwyKUBICVBqbUWc0KbM=; b=g3aQoNkPyJccBSuqqDMHBAAJ49/6UwtWuRLcTU8+ISS18r87Va4uyxgpKPdbhq2urS W7AJYKSUxHMYYIalPh4QW3m/hVB21UgOMoxc2vGfmasX/yK/m8GC168RmIU8wcNwp59C 8jKOaL0iMFqGqDpz95FmXuq+MN9pFGV50ix6M= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=KxrWCS3SPpl7pa5aaAWG2MUZ/27LbxwXwdtp/Qo6GMDV9CWX1vGgoHyGBX5Y5ilyA3 Frk6rYFSORvTid3XrHhunSqgigwviURIW/4njiY1mwU8fb8fq6QcIvPvogBjn306U3o1 00PE4nm0flVEhgXgXoYcGu2EyBDXrNJodTaCE= MIME-Version: 1.0 Received: by 10.140.226.1 with HTTP; Thu, 8 Apr 2010 09:09:01 -0700 (PDT) In-Reply-To: <1270673488.8771.166.camel@erebus.lan> References: <1270673488.8771.166.camel@erebus.lan> Date: Thu, 8 Apr 2010 09:09:01 -0700 Received: by 10.141.23.21 with SMTP id a21mr518778rvj.50.1270742942012; Thu, 08 Apr 2010 09:09:02 -0700 (PDT) Message-ID: Subject: Re: Heap sudden jump during import From: Tatu Saloranta To: user@cassandra.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org On Wed, Apr 7, 2010 at 1:51 PM, Eric Evans wrote: > On Tue, 2010-04-06 at 10:55 -0700, Tatu Saloranta wrote: >> On Tue, Apr 6, 2010 at 12:15 AM, JKnight JKnight >> wrote: >> > When import, all data in json file will load in memory. So that, you >> can not >> > import large data. >> > You need to export large sstable file to many small json files, and >> run >> > import. >> >> Why would you ever read the whole file in memory? JSON is very easily >> streamable. Or does the whole data set need to be validated or >> something (I assume not, if file splitting could be used). Perhaps it >> is just an implementation flaw in importer tool. > > It's been awhile, but if I'm not mistaken, this is because we're writing > SSTables and the records must be written in decorated-key sorted order. Ok. It might make sense to solve this then, for example by using external sorting? (reminds me that I must clean up and release basic on-disk merge sort code that seems to be something that is not included in existing commons lib, oddly enough -- we used it for this purpose, pre-sorting data for systems that required it, or benefited heavily) -+ Tatu +-