From cassandra-user-return-1852-apmail-incubator-cassandra-user-archive=incubator.apache.org@incubator.apache.org Wed Dec 16 23:23:41 2009 Return-Path: Delivered-To: apmail-incubator-cassandra-user-archive@minotaur.apache.org Received: (qmail 52412 invoked from network); 16 Dec 2009 23:23:41 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 16 Dec 2009 23:23:41 -0000 Received: (qmail 4178 invoked by uid 500); 16 Dec 2009 23:23:41 -0000 Delivered-To: apmail-incubator-cassandra-user-archive@incubator.apache.org Received: (qmail 4151 invoked by uid 500); 16 Dec 2009 23:23:41 -0000 Mailing-List: contact cassandra-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cassandra-user@incubator.apache.org Delivered-To: mailing list cassandra-user@incubator.apache.org Received: (qmail 4142 invoked by uid 99); 16 Dec 2009 23:23:41 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Dec 2009 23:23:41 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of bburruss@real.com designates 207.188.23.6 as permitted sender) Received: from [207.188.23.6] (HELO jor-el.real.com) (207.188.23.6) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Dec 2009 23:23:33 +0000 Received: from seacas02.corp.real.com ([::ffff:192.168.139.57]) (TLS: TLSv1/SSLv3,128bits,AES128-SHA) by jor-el.real.com with esmtp; Wed, 16 Dec 2009 15:23:11 -0800 id 00094065.4B296BDF.00005771 Received: from seambx.corp.real.com ([fe80::2d15:fda7:b3b8:e268]) by seacas02.corp.real.com ([::1]) with mapi; Wed, 16 Dec 2009 15:23:11 -0800 From: Brian Burruss To: "cassandra-user@incubator.apache.org" Date: Wed, 16 Dec 2009 15:21:54 -0800 Subject: RE: OOM Exception Thread-Topic: OOM Exception Thread-Index: Acp+pkyedrS5tmCwTm6FRL+fd0RoqwAAEFFq Message-ID: <766B5A29D28DA442AB229AAEE2AFC44507D7B914F8@SEAMBX.corp.real.com> References: <766B5A29D28DA442AB229AAEE2AFC44507D7B914F6@SEAMBX.corp.real.com>, In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org sorry, thought i included everything ;) however, i am using beta2 ________________________________________ From: Jonathan Ellis [jbellis@gmail.com] Sent: Wednesday, December 16, 2009 3:18 PM To: cassandra-user@incubator.apache.org Subject: Re: OOM Exception What version are you using? 0.5 beta2 fixes the using-more-memory-on-startup problem. On Wed, Dec 16, 2009 at 5:16 PM, Brian Burruss wrote: > i'll put my question first: > > - how can i determine how much RAM is required by cassandra? (for normal= operation and restarting server) > > *** i've attached my storage-conf.xml > > i've gotten several more OOM exceptions since i mentioned it a week or so= ago. i started from a fresh database a couple days ago and have been addi= ng 2k blocks of data keyed off a random integer at the rate of about 400/se= c. i have a 2 node cluster, RF=3D2, Consistency for read/write is ONE. th= ere are ~70,420,082 2k blocks of data in the database. > > i used the default memory setup of Xmx1G when i started a couple days ago= . as the database grew to ~180G (reported by unix du command) both servers= OOM'ed at about the same time, within 10 minutes of each other. well need= less to say, my cluster is dead. so i upped the memory to 3G and the serve= rs tried to come back up, but one died again with OOM. > > Before cleaning the disk and starting over a couple days ago, i played th= e game of "jack up the RAM", but eventually i didn't want to up it anymore = when i got to 5G. the parameter, SSTable.INDEX_INTERVAL, was discussed a f= ew days ago that would change the number of "keys" cached in memory, so i c= ould modify that at the cost of read performance, but doing the math, 3G sh= ould be plenty of room. > > it seems like startup requires more RAM than just normal running. > > so this of course concerns me. > > i have the hprof files from when the server initially crashed and when it= crashed trying to restart if anyone wants them >