Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 37088 invoked from network); 27 May 2010 16:33:57 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 27 May 2010 16:33:57 -0000 Received: (qmail 41504 invoked by uid 500); 27 May 2010 16:33:56 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 41480 invoked by uid 500); 27 May 2010 16:33:56 -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 41472 invoked by uid 99); 27 May 2010 16:33:56 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 May 2010 16:33:55 +0000 X-ASF-Spam-Status: No, hits=1.5 required=10.0 tests=AWL,HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [207.5.72.164] (HELO EXHUB016-2.exch016.msoutlookonline.net) (207.5.72.164) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 May 2010 16:33:50 +0000 Received: from EXVMBX016-3.exch016.msoutlookonline.net ([207.5.72.173]) by EXHUB016-2.exch016.msoutlookonline.net ([207.5.72.164]) with mapi; Thu, 27 May 2010 09:33:29 -0700 From: Daniel Kluesing To: "user@cassandra.apache.org" Date: Thu, 27 May 2010 09:33:22 -0700 Subject: RE: Continuously increasing RAM usage Thread-Topic: Continuously increasing RAM usage Thread-Index: Acr9tmmKHxOfq3I5RMS7igxXG1JVBwAAshpA Message-ID: <33FDEB0CE2F65F41A4CF8769247BB3668DCE778C39@EXVMBX016-3.exch016.msoutlookonline.net> References: <4BFE94F0.8070005@digg.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: multipart/alternative; boundary="_000_33FDEB0CE2F65F41A4CF8769247BB3668DCE778C39EXVMBX0163exc_" MIME-Version: 1.0 --_000_33FDEB0CE2F65F41A4CF8769247BB3668DCE778C39EXVMBX0163exc_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 0.6.0 had some gc issues, (I think https://issues.apache.org/jira/browse/CA= SSANDRA-1014) if you see lots of gc collections in the logs, I'd give 0.6.1= a try, I found it much better. Anecdotally, the sun jvm performs better than openJDK, and the u19 drop fix= es some jvm bugs that can cause memory problems. Sun jvm, u19 (or higher) a= nd Cassandra 0.6.1 fixed a lot of memory problems I ran into. From: James Golick [mailto:jamesgolick@gmail.com] Sent: Thursday, May 27, 2010 9:05 AM To: user@cassandra.apache.org Subject: Re: Continuously increasing RAM usage When I say unresponsive, I mean that latency becomes very high. Swap is tur= ned off, but before I turned it on, it used to swap heavily at this point. Cassandra version is 0.6.0 Beta1 [cassandra1 ~]# java -version java version "1.6.0" OpenJDK Runtime Environment (build 1.6.0-b09) OpenJDK 64-Bit Server VM (build 1.6.0-b09, mixed mode) Here is the tpstats from a node that was restarted last night: http://gist.github.com/415987 On Thu, May 27, 2010 at 8:51 AM, Robert Coli > wrote: On 5/26/10 11:32 PM, James Golick wrote: We're seeing RAM usage continually climb until eventually, cassandra become= s unresponsive. Given the handful of bugs related to memory bloat in specific versions of C= assandra combined with specific versions of JVMs, that information may be r= elevant to your question. What version are you running, and in what JVM env= ironment? =3DRob --_000_33FDEB0CE2F65F41A4CF8769247BB3668DCE778C39EXVMBX0163exc_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

0.6.0 had some gc issues, (I think https://issues.apache.org= /jira/browse/CASSANDRA-1014) if you see lots of gc collections in the logs, I’d give 0.6.1 a try, = I found it much better.

 

Anecdotally, the sun jvm performs better than openJDK, and t= he u19 drop fixes some jvm bugs that can cause memory problems. Sun jvm, u19 (= or higher) and Cassandra 0.6.1 fixed a lot of memory problems I ran into.=

 

From: James Golick [mailto:jamesgolick@gmail.com]
Sent: Thursday, May 27, 2010 9:05 AM
To: user@cassandra.apache.org
Subject: Re: Continuously increasing RAM usage

 

When I say unresponsive, I mean that latency becomes v= ery high. Swap is turned off, but before I turned it on, it used to swap heavil= y at this point.

 

Cassandra version is 0.6.0 Beta1

 

[cassandra1 ~]# java -version

java version "1.6.0"

OpenJDK  Runtime Environment (build 1.6.0-b09)

OpenJDK 64-Bit Server VM (build 1.6.0-b09, mixed mode)=

 

Here is the tpstats from a node that was restarted las= t night:

 

 

On Thu, May 27, 2010 at 8:51 AM, Robert Coli <rcoli@digg.com> wrote:

On 5/26/10 11:32 PM, James Golick wrote:

We're seeing RAM usage continually climb until eventua= lly, cassandra becomes unresponsive.

Given the handful of bu= gs related to memory bloat in specific versions of Cassandra combined with specific versions of JVMs, that information may be relevant to your questio= n. What version are you running, and in what JVM environment?

=3DRob

 

--_000_33FDEB0CE2F65F41A4CF8769247BB3668DCE778C39EXVMBX0163exc_--