From user-return-60639-archive-asf-public=cust-asf.ponee.io@cassandra.apache.org Wed Apr 4 14:30:40 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 15DCF18064F for ; Wed, 4 Apr 2018 14:30:39 +0200 (CEST) Received: (qmail 46765 invoked by uid 500); 4 Apr 2018 12:30:38 -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 46755 invoked by uid 99); 4 Apr 2018 12:30:38 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Apr 2018 12:30:38 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id AAD78C03D9 for ; Wed, 4 Apr 2018 12:30:37 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.888 X-Spam-Level: ** X-Spam-Status: No, score=2.888 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_REPLY=1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id ImFckwp3_e0K for ; Wed, 4 Apr 2018 12:30:36 +0000 (UTC) Received: from sonic310-13.consmr.mail.bf2.yahoo.com (sonic310-13.consmr.mail.bf2.yahoo.com [74.6.135.123]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id DEE875F124 for ; Wed, 4 Apr 2018 12:30:35 +0000 (UTC) X-YMail-OSG: kuqGtRMVM1k75B49bIJO9mFf99OsIHebSdoWl8HbqtFBZYgA8x_QiWYrbGDFsUB CPTYcaeRxibDcfWD9yVxG5QKMhZti4Ajf7rwG9FMSGmVKTvErpM29vOx5AGenUYCHtbLSJi6748J QeJw0Guy3i5qFvMo_IVyhWzkg3nJc13TuRDGjE1MvWyDM6uxrfqVr1nUqIXvDC1Owl8RpzYHWBAf VR7JJAyzuqUdybwCHHGgul_izpKJdj41HQNr2r3z.VIg5kR8OTiBthZAnmVuCBHbAT3C7IxhO05h aG9evAdZY6cKnXFIDA3rhMVKwL95nte.rCl2vBSwz8fJdfD044GDYGJ.HZude59l.NFDd0gS3u.s naldj1kWWGCXFLgBrCm0MXERYhfeZhpdJOmiBpZO5GvrZZW5BOvg9HEElbfswhpAEtQ4MgRIbzUe lwYvTAajFbKMolVgTpueMqFRxm0q3nbVDw6f3bdwj.95cooqiTveHJyhPPK2A21.EC7EtZC2k4DU 4DeVv9ZsG48G7_Ms5vQ-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic310.consmr.mail.bf2.yahoo.com with HTTP; Wed, 4 Apr 2018 12:30:34 +0000 Received: from c-73-116-39-136.hsd1.ca.comcast.net (EHLO i7) ([73.116.39.136]) by smtp425.mail.bf1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID b62053d13042b2a2acff2cac4547e436 for ; Wed, 04 Apr 2018 12:30:34 +0000 (UTC) From: "Kenneth Brotman" To: References: <5493B5D7FE44FE46AF0190D470C9052F0192A296@ZSZExchange.ZS-Zweiradteile.local> <0b7ced75-b555-45a2-b0ce-a4b4313d1ffb@Spark> In-Reply-To: <0b7ced75-b555-45a2-b0ce-a4b4313d1ffb@Spark> Subject: RE: Urgent Problem - Disk full Date: Wed, 4 Apr 2018 05:30:32 -0700 Message-ID: <000301d3cc10$ba51c360$2ef54a20$@yahoo.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0004_01D3CBD6.0DF44AF0" X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQIsakwPbR8lkpr0WDpZSQrkMEIGgwHZ4bIOozB9KJA= Content-Language: en-us ------=_NextPart_000_0004_01D3CBD6.0DF44AF0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Assuming the data model is good and there haven=E2=80=99t been any = sudden jumps in memory use, it seems like the normal thing to do is = archive some of the old time series data that you don=E2=80=99t care = about. =20 Kenneth Brotman =20 From: Rahul Singh [mailto:rahul.xavier.singh@gmail.com]=20 Sent: Wednesday, April 04, 2018 4:38 AM To: user@cassandra.apache.org; user@cassandra.apache.org Subject: Re: Urgent Problem - Disk full =20 Nothing a full repair won=E2=80=99t be able to fix.=20 On Apr 4, 2018, 7:32 AM -0400, J=C3=BCrgen Albersdorfer = , wrote: Hi, I have an urgent Problem. - I will run out of disk space in near future. Largest Table is a Time-Series Table with TimeWindowCompactionStrategy = (TWCS) and default_time_to_live =3D 0 Keyspace Replication Factor RF=3D3. I run C* Version 3.11.2 We have grown the Cluster over time, so SSTable files have different = Dates on different Nodes. From Application Standpoint it would be safe to loose some of the oldest = Data. Is it safe to delete some of the oldest SSTable Files, which will no = longer get touched by TWCS Compaction any more, while Node is clean = Shutdown? - And doing so for one Node after another? Or maybe there is a different way to free some disk space? - Any = suggestions? best regards J=C3=BCrgen Albersdorfer --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@cassandra.apache.org For additional commands, e-mail: user-help@cassandra.apache.org ------=_NextPart_000_0004_01D3CBD6.0DF44AF0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Assuming the data model is good and there haven=E2=80=99t been any = sudden jumps in memory use, it seems like the normal thing to do is = archive some of the old time series data that you don=E2=80=99t care = about.

 

Kenneth Brotman

 

From:= = Rahul Singh [mailto:rahul.xavier.singh@gmail.com]
Sent: = Wednesday, April 04, 2018 4:38 AM
To: = user@cassandra.apache.org; user@cassandra.apache.org
Subject: = Re: Urgent Problem - Disk full

 

Nothing a = full repair won=E2=80=99t be able to = fix. 


On Apr = 4, 2018, 7:32 AM -0400, J=C3=BCrgen Albersdorfer <Juergen.Albersdorfe= r@zweiradteile.net>, wrote:

Hi,

I = have an urgent Problem. - I will run out of disk space in near = future.
Largest Table is a Time-Series Table with = TimeWindowCompactionStrategy (TWCS) and default_time_to_live =3D = 0
Keyspace Replication Factor RF=3D3. I run C* Version 3.11.2
We = have grown the Cluster over time, so SSTable files have different Dates = on different Nodes.

From Application Standpoint it would be safe = to loose some of the oldest Data.

Is it safe to delete some of = the oldest SSTable Files, which will no longer get touched by TWCS = Compaction any more, while Node is clean Shutdown? - And doing so for = one Node after another?

Or maybe there is a different way to free = some disk space? - Any suggestions?

best regards
J=C3=BCrgen = Albersdorfer

-----------------------------------------------------= ----------------
To unsubscribe, e-mail: user-unsubscribe@ca= ssandra.apache.org
For additional commands, e-mail: user-help@cassandra.apache= .org

------=_NextPart_000_0004_01D3CBD6.0DF44AF0--