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 B51CD18E95 for ; Sat, 13 Feb 2016 07:48:27 +0000 (UTC) Received: (qmail 81814 invoked by uid 500); 13 Feb 2016 07:48:24 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 81773 invoked by uid 500); 13 Feb 2016 07:48:24 -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 81763 invoked by uid 99); 13 Feb 2016 07:48:24 -0000 Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 13 Feb 2016 07:48:24 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 584E4180495 for ; Sat, 13 Feb 2016 07:48:24 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.279 X-Spam-Level: * X-Spam-Status: No, score=1.279 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=spanning-com.20150623.gappssmtp.com Received: from mx2-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id 9uAFD7bMiPW0 for ; Sat, 13 Feb 2016 07:48:23 +0000 (UTC) Received: from mail-vk0-f46.google.com (mail-vk0-f46.google.com [209.85.213.46]) by mx2-lw-us.apache.org (ASF Mail Server at mx2-lw-us.apache.org) with ESMTPS id ECB1D5FC11 for ; Sat, 13 Feb 2016 07:48:22 +0000 (UTC) Received: by mail-vk0-f46.google.com with SMTP id e185so76431743vkb.1 for ; Fri, 12 Feb 2016 23:48:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=spanning-com.20150623.gappssmtp.com; s=20150623; h=mime-version:date:message-id:subject:from:to:content-type; bh=0vAXM9YGtK675Ucwg77VekhZmdbCV7AiZ1Ro5yJ4BnU=; b=BM9+DAlH66zXww/5ozlK956YmUJ9PAogYz5LIgTuylA5dUM05hNCYMV2/cf401c0ur jSUGDQcO1v51d1/R4eVewgRY0Ko1ypnW83FFjMYtJM8dPXkI00+zCqm5NlRFMxhZcDr1 DNapNjK+sl7eupDgZM/b8Ey/mR/1xqFtr9RJqsOa+s3V1cljIjIYcCiAU2ce9x3THp+W pzMBTJWrcbuPZX4mB9xWL+MxLN5BT/eUWSd320KZoSUTzTTD3vZBUf880CB5ITrPxPOT 2tnUEj9lbPQxQBLvQUt+XjveLb7v0shcqoBA6tSkq5Qf5dP+ESYu2h9L7Ul1eQju74fW 2s+w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=0vAXM9YGtK675Ucwg77VekhZmdbCV7AiZ1Ro5yJ4BnU=; b=A8wUBn8m9ec6vrucNiunn38y+jotWpF1E04+fpQrKFMp1ehKD8uaLZS82eXVzceOfM MlJM2ehTgdwwYZQALt66NgiEUXGAuciGKhQScJMWOnmoA0Mcl7Iny0xLZkOTJWF5sBiS Nyr+t6Pq+AoQ7FbIhZsuYjz9H+Z2eQfdQT60JtIu4moJelUcgy8QMXPNl/o1FbwHayb9 5LYx+J7bocvHOd25NpU96C6RvzODGq0Ay57W+o3/ZTr3+6Zt7/RLzqq3twnNy2xcCBr/ iNCp0zeEbQ1Do22/wzuQ+PUX45L88Ws43ZwjGnyf/Jf2RZzlaqMVrh36FoH8qjr61o+C 0fHw== X-Gm-Message-State: AG10YOTQzjHgb3Cpj2qGTBNgg8KWZD7bGtIxS/sq83RWouM72O/bLoAhLcx1ITWocbIUYJ7axecJuHaLqbluOg== MIME-Version: 1.0 X-Received: by 10.31.13.79 with SMTP id 76mr4543533vkn.148.1455349696001; Fri, 12 Feb 2016 23:48:16 -0800 (PST) Received: by 10.159.39.230 with HTTP; Fri, 12 Feb 2016 23:48:15 -0800 (PST) Date: Sat, 13 Feb 2016 01:48:15 -0600 Message-ID: Subject: Sudden disk usage From: Branton Davis To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=001a11440cf8a7c2cc052ba201ad --001a11440cf8a7c2cc052ba201ad Content-Type: text/plain; charset=UTF-8 One of our clusters had a strange thing happen tonight. It's a 3 node cluster, running 2.1.10. The primary keyspace has RF 3, vnodes with 256 tokens. This evening, over the course of about 6 hours, disk usage increased from around 700GB to around 900GB on only one node. I was at a loss as to what was happening and, on a whim, decided to run nodetool cleanup on the instance. I had no reason to believe that it was necessary, as no nodes were added or tokens moved (not intentionally, anyhow). But it immediately cleared up that extra space. I'm pretty lost as to what would have happened here. Any ideas where to look? Thanks! --001a11440cf8a7c2cc052ba201ad Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
One of our clusters had a strange thing happen tonight.=C2= =A0 It's a 3 node cluster, running 2.1.10.=C2=A0 The primary keyspace h= as RF 3, vnodes with 256 tokens.

This evening, over the = course of about 6 hours, disk usage increased from around 700GB to around 9= 00GB on only one node.=C2=A0 I was at a loss as to what was happening and, = on a whim, decided to run nodetool cleanup on the instance.=C2=A0 I had no = reason to believe that it was necessary, as no nodes were added or tokens m= oved (not intentionally, anyhow).=C2=A0 But it immediately cleared up that = extra space.

I'm pretty lost as to what would = have happened here.=C2=A0 Any ideas where to look?

Thanks!

--001a11440cf8a7c2cc052ba201ad--