Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 90914 invoked from network); 15 Jun 2010 17:00:10 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 15 Jun 2010 17:00:10 -0000 Received: (qmail 8484 invoked by uid 500); 15 Jun 2010 17:00:09 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 8403 invoked by uid 500); 15 Jun 2010 17:00:08 -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 8395 invoked by uid 99); 15 Jun 2010 17:00:08 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Jun 2010 17:00:08 +0000 X-ASF-Spam-Status: No, hits=0.7 required=10.0 tests=RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.211.181] (HELO mail-yw0-f181.google.com) (209.85.211.181) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Jun 2010 17:00:01 +0000 Received: by ywh11 with SMTP id 11so3840000ywh.7 for ; Tue, 15 Jun 2010 09:59:39 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.185.1 with SMTP id cm1mr3335307qcb.57.1276621176863; Tue, 15 Jun 2010 09:59:36 -0700 (PDT) Received: by 10.229.233.202 with HTTP; Tue, 15 Jun 2010 09:59:36 -0700 (PDT) In-Reply-To: <001c01cb0ca9$ac579b60$0506d220$@com> References: <001c01cb0ca9$ac579b60$0506d220$@com> Date: Tue, 15 Jun 2010 09:59:36 -0700 Message-ID: Subject: Re: java.lang.OutofMemoryerror: Java heap space From: Benjamin Black To: user@cassandra.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org You should only have to restart once per node to pick up config changes. On Tue, Jun 15, 2010 at 9:41 AM, caribbean410 wrot= e: > Today I retry the 2GB heap now it's working. No that out of memory error. > Looks like I have to restart Cassandra several times before the new chang= es > take effect. > > -----Original Message----- > From: Benjamin Black [mailto:b@b3k.us] > Sent: Monday, June 14, 2010 7:46 PM > To: user@cassandra.apache.org > Subject: Re: java.lang.OutofMemoryerror: Java heap space > > My guess: you are outrunning your disk I/O. =A0Each of those 5MB rows > gets written to the commitlog, and the memtable is flushed when it > hits the configured limit, which you've probably left at 128MB. =A0Every > 25 rows or so you are getting memtable flushed to disk. =A0Until these > things complete, they are in RAM. > > If this is actually representative of your production use, you need a > dedicated commitlog disk, several drives in RAID0 or RAID10 for data, > a lot more RAM, and much larger memtable flush size. > > > b > > On Mon, Jun 14, 2010 at 6:13 PM, Caribbean410 > wrote: >> Hi, >> >> I wrote 200k records to db with each record 5MB. Get this error when I > uses >> 3 threads (each thread tries to read 200k record totally, 100 records a >> time) to read data from db. The write is OK, the error comes from read. >> Right now the Xmx of JVM is 1GB. I changed it to 2GB, still not working. > If >> the record size is under 4K, I will not get this error. Any clues to avo= id >> this error? >> >> Thx >> > >