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 A595DE714 for ; Wed, 13 Mar 2013 17:11:55 +0000 (UTC) Received: (qmail 21312 invoked by uid 500); 13 Mar 2013 17:11:53 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 21264 invoked by uid 500); 13 Mar 2013 17:11: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 21256 invoked by uid 99); 13 Mar 2013 17:11:52 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Mar 2013 17:11:52 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of arodrime@gmail.com designates 209.85.215.47 as permitted sender) Received: from [209.85.215.47] (HELO mail-la0-f47.google.com) (209.85.215.47) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Mar 2013 17:11:46 +0000 Received: by mail-la0-f47.google.com with SMTP id fj20so1398091lab.20 for ; Wed, 13 Mar 2013 10:11:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:from:date:message-id:subject:to :content-type; bh=brd51JvdRW+mDkFFH58/++Y4Twj++p48TJtXRKXaRv0=; b=ovTR9ZCNlX1Dcaeubv6WU7wXP/PbRA6dA3f2lb6/Zzvk1rgEcxH15zOv4gT7R1N5+u 3//YuuA0Dg7BGs6aAQpSrzGuwYrO2P0HQD2LJs/1D/DRWve0D9tMQMn5zUT9vunx65DV ogxOV3caTqvB6wVXyckGc4CbhZGF3Gc9DLKH1wkpo08NGSIPLEkFX8FppDP7cym3yEDb drfDHnpcoEfcGqrat+4zJoKITa+ceZL1Qe7Sgg7aCvqLLZHy9Rn9meSDExbPsw6mKbBY riSmBBdkWaO69v0alJaXWgQFeDmCruLr/J+razBe+mTdJuKyoiJYbt60WrZDlJziYcV+ 7AzA== X-Received: by 10.112.84.228 with SMTP id c4mr7825838lbz.113.1363194685688; Wed, 13 Mar 2013 10:11:25 -0700 (PDT) MIME-Version: 1.0 Received: by 10.112.44.230 with HTTP; Wed, 13 Mar 2013 10:11:04 -0700 (PDT) From: Alain RODRIGUEZ Date: Wed, 13 Mar 2013 18:11:04 +0100 Message-ID: Subject: About the heap To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=f46d04016b3b00183d04d7d17f7f X-Virus-Checked: Checked by ClamAV on apache.org --f46d04016b3b00183d04d7d17f7f Content-Type: text/plain; charset=ISO-8859-1 Hi, I would like to know everything that is in the heap. We are here speaking of C*1.1.6 Theory : - Memtable (1024 MB) - Key Cache (100 MB) - Row Cache (disabled, and serialized with JNA activated anyway, so should be off-heap) - BloomFilters (about 1,03 GB - from cfstats, adding all the "Bloom Filter Space Used" and considering they are showed in Bytes - 1103765112) - Anything else ? So my heap should be fluctuating between 1,15 GB and 2.15 GB and growing slowly (from the new BF of my new data). My heap is actually changing from 3-4 GB to 6 GB and sometimes growing to the max 8 GB (crashing the node). Because of this I have an unstable cluster and have no other choice than use Amazon EC2 xLarge instances when we would rather use twice more EC2 Large nodes. What am I missing ? Practice : Is there a way not inducing any load and easy to do to dump the heap to analyse it with MAT (or anything else that you could advice) ? Alain --f46d04016b3b00183d04d7d17f7f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,

I would like to know everythi= ng that is in the heap.

We are here sp= eaking of C*1.1.6

Theory :

- Memtable (1024 MB)
- Key Cache (= 100 MB)
- Row Cache (disabled, and serialized with JNA acti= vated anyway, so should be off-heap)
- BloomFilters (about = 1,03 GB - from cfstats, adding all the "Bloom Filter Space Used" = and considering they are showed in Bytes - 1103765112)
- Anything else ?

So my hea= p should be fluctuating between 1,15 GB and 2.15 GB and growing slowly (fro= m the new BF of my new data).

My heap = is actually changing from 3-4 GB to 6 GB and sometimes growing to the max 8= GB (crashing the node).

Because of this I have an unstable cluster = and have no other choice than use Amazon EC2 xLarge instances when we would= rather use twice more EC2 Large nodes.

What am I missing ?

Practice :

Is there a way not inducing any load and easy= to do to dump the heap to analyse it with MAT (or anything else that you c= ould advice) ?

Alain
--f46d04016b3b00183d04d7d17f7f--