Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D2A03DF36 for ; Wed, 22 Aug 2012 04:28:54 +0000 (UTC) Received: (qmail 38641 invoked by uid 500); 22 Aug 2012 04:28:52 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 38516 invoked by uid 500); 22 Aug 2012 04:28:52 -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 38505 invoked by uid 99); 22 Aug 2012 04:28:52 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Aug 2012 04:28:52 +0000 X-ASF-Spam-Status: No, hits=2.6 required=5.0 tests=FROM_LOCAL_NOVOWEL,HK_RANDOM_ENVFROM,HK_RANDOM_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of xrjxrjxrjnet@gmail.com designates 209.85.160.44 as permitted sender) Received: from [209.85.160.44] (HELO mail-pb0-f44.google.com) (209.85.160.44) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Aug 2012 04:28:47 +0000 Received: by pbbrr4 with SMTP id rr4so846573pbb.31 for ; Tue, 21 Aug 2012 21:28:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=A/eT7igYeQIwi7NAvJxF7QrNKbasHMqTvUYEa6bjVTg=; b=0T4GfkIebJgXn5g8chiWYGoYNTa+t+7ilhwkwvPNJdAhqtrYClPFWqDCHMvRXsU3pz q+Qvsl5KrxlbV2xHJB43ipLZPZYmSMryakEE7FejJQ4WW/uw+iVKJwovTosiiKh9NrG0 aDfKvoqYILfywGvODg9ST+hLzbmISqQ1dJ7DtL6zP5CIpSGGQ+i57jqcGKPtM1E1FC/Y 0QCbqkoZJzd9teUMiK6FbCeKhsppJ9TAZDDoxkUCRhtIZV8J2GQR+T0qgmhRXnxHKHA9 GCCCUYozzz8QWv3NbUAoJmsHwMTEaLi3rAJEAstMWS3CPmROq01lqZNoE0gEpj+SgppW cvWA== MIME-Version: 1.0 Received: by 10.68.224.161 with SMTP id rd1mr30639823pbc.133.1345609706764; Tue, 21 Aug 2012 21:28:26 -0700 (PDT) Received: by 10.66.84.3 with HTTP; Tue, 21 Aug 2012 21:28:26 -0700 (PDT) In-Reply-To: References: Date: Wed, 22 Aug 2012 12:28:26 +0800 Message-ID: Subject: Re: OutOfMemory log in Cassandra From: Xu Renjie To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=e89a8ff24ff693f97c04c7d32c86 X-Virus-Checked: Checked by ClamAV on apache.org --e89a8ff24ff693f97c04c7d32c86 Content-Type: text/plain; charset=ISO-8859-1 Guille, Thanks for your reply. I seem to find where is the problem. I guess it is because memory is used up not the jvm heap( I use micro ec2 instance just for toy use). Seems that I have set the cassandra heap too high to avoid gc to effect my performance, but the total memory is not enough. So I have set a smaller cache value for my application. Currently, it works well. On Wed, Aug 22, 2012 at 11:42 AM, Guillermo Winkler < gwinkler@inconcertcc.com> wrote: > Xu, what's your configuration? > > How many CF, how much data (size/rows/cols), how many clients > operations/sec and how much memory assigned for the heap? > > Guille > > > On Wed, Aug 22, 2012 at 12:09 AM, Xu Renjie wrote: > >> Hi, all >> I have a problem about the log. I have set the CASSANDRA_HEAPDUMP_DIR >> in the cassandra-env.in file to some path to store the dump file >> when OutOfMemory exception happens. But after out of memory happens(I >> judge it from the /var/log/messages which says "kernel: out of memory: >> kill process XXXX), there is no dump file generated in that path. Is this >> because kernel kill the jvm first so no OutOfMemory exception thrown or >> what? I am new to linux. Thanks in advance. >> >> > --e89a8ff24ff693f97c04c7d32c86 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Guille,=A0
=A0 =A0Thanks for your reply. I seem to find where is the pr= oblem. I guess it is because memory is used up not the jvm heap( I use micr= o ec2 instance just for toy use). Seems that I have set the cassandra heap = too high to avoid gc to effect my performance, but the total memory is not = enough. So I have set a smaller cache value for my application. Currently, = it works well.

On Wed, Aug 22, 2012 at 11:42 AM, Guillermo = Winkler <gwinkler@inconcertcc.com> wrote:
Xu, what's your configuration?

How many CF, how much= data (size/rows/cols), how many clients operations/sec and how much memory= assigned for the heap?

Guille


On Wed, Aug 22, 2012 at 12:09 AM, Xu Renjie <xrjxrjxrjnet@gmail.com> wrote:
Hi, all
=A0 =A0I have a problem about the log. I have set the CASSANDRA= _HEAPDUMP_DIR in the = cassandra-env.in file to some path to store the dump file
whe= n OutOfMemory exception happens. But after out of memory happens(I judge it= from the /var/log/messages which says "kernel: out of memory:
kill process XXXX), there is no dump file generated in that path. Is t= his because kernel kill the jvm first so no OutOfMemory exception thrown or= what? I am new=A0to linux. Thanks in advance.



--e89a8ff24ff693f97c04c7d32c86--