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 465FA4F29 for ; Sat, 21 May 2011 08:41:00 +0000 (UTC) Received: (qmail 3516 invoked by uid 500); 21 May 2011 08:40:57 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 3464 invoked by uid 500); 21 May 2011 08:40: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 3456 invoked by uid 99); 21 May 2011 08:40:56 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 21 May 2011 08:40:56 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jonathan.colby@gmail.com designates 209.85.214.44 as permitted sender) Received: from [209.85.214.44] (HELO mail-bw0-f44.google.com) (209.85.214.44) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 21 May 2011 08:40:48 +0000 Received: by bwz13 with SMTP id 13so4101552bwz.31 for ; Sat, 21 May 2011 01:40:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:content-type:content-transfer-encoding :subject:date:message-id:to:mime-version:x-mailer; bh=T1xLkrUz/C4Py9cnFzQjByNUNdi/bmh87Cp3Aj3CoNM=; b=eVvSaGK8sY5W28a/65thHR3CVrULbdMGRSpsQD4FrKEnbBrszPXnZSKJrCAcmNlT9T vnKg6DNsVSfD6f1mJFRN8Pza6EcAkOv9bfICC0J8PlpAXfvyKi1Iu0Eu4fsYUZ26INbI +AN9VjvIkZKISAIR0Mn9G4DSAMarP2+QHzZPE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:message-id :to:mime-version:x-mailer; b=DxtJNzKI+kgxV4uxrNJwf7tSutIAk/1q3EkyropsA1biDWTjHIdUsTbtPCQoh1L7qv ZSN2LA1DGllGSn/Q6y9RWSS0nZDg+g4av/jLCWO6CpFpUw6SGuHm6ctUKqG1C9c5aH0a EAlkOlHaZsX7JLzQbA7C7+55egBeXwYNpLe4g= Received: by 10.204.145.18 with SMTP id b18mr424814bkv.26.1305967227400; Sat, 21 May 2011 01:40:27 -0700 (PDT) Received: from [192.168.1.102] (f052052245.adsl.alicedsl.de [78.52.52.245]) by mx.google.com with ESMTPS id q24sm2601132bks.9.2011.05.21.01.40.24 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 21 May 2011 01:40:25 -0700 (PDT) From: Jonathan Colby Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: extremely high temporary disk utilization 0.7.5 Date: Sat, 21 May 2011 10:40:22 +0200 Message-Id: <7196125E-9F5E-49E3-A391-1DD85E4762D3@gmail.com> To: user@cassandra.apache.org Mime-Version: 1.0 (Apple Message framework v1084) X-Mailer: Apple Mail (2.1084) On each of our nodes we have an average of 80 - 100 GB actual cassandra = data on 1 TB disks. There is normally plenty of capacity on the = nodes. Swap is OFF. OS is Debian 64 bit. Every once in a while, the disk usage will skyrocket to 500+ GB, even = once filling up the 1 TB disk (at least according to linux df). The thing is, after restarting the cassandra daemon, the disk usage = correctly reflects the actual data usage. =20 What could be causing this massive temporary disk allocation? Is it malloc? Is this an indication that something is not configured = correctly? Is this a bug? Any help would be appreciated! Jon