from TTL 0 to 10 days. This might mean that some data are not deleted
>> because at some point in time were written with no TTL ( TTL set to 0).
>>
>> This has occurred in some systems in past.
>>
>> You may use the sstableexpiredblocker tool to check about this.
>>
>>
>&
lliam Crowell
>
>
>
> *From: *C. Scott Andreas
> *Date: *Friday, March 21, 2025 at 12:21 AM
> *To: *user@cassandra.apache.org
> *Cc: *user@cassandra.apache.org
> *Subject: *Re: Increased Disk Usage After Upgrading From Cassandra 3.x.x
> to 4.1.3
>
> You don't of
the sstableexpiredblocker tool to check about this.
BR
MK
From: William Crowell via user
Sent: March 20, 2025 13:58
To: user@cassandra.apache.org
Cc: William Crowell ; Sartor Fabien (DIN)
; tasmaniede...@free.fr
Subject: Re: Increased Disk Usage After Upgrading From Cassandra 3.x.x to 4.1.3
pache.org ; Stéphane
>> Alleaume
>> *Cc:* William Crowell ; sc...@paradoxica.net <
>> sc...@paradoxica.net>; asf.telli...@gmail.com
>> *Subject:* [EXTERNAL] Re: Increased Disk Usage After Upgrading From
>> Cassandra 3.x.x to 4.1.3
>>
>> Good mornin
rch 14, 2025 at 10:53 AM
To: user@cassandra.apache.org<mailto:user@cassandra.apache.org>
<mailto:user@cassandra.apache.org>
Cc: William Crowell <mailto:wcrow...@perforce.com>,
Bowen Song <mailto:bo...@bso.ng>
Subject: Re: Increased Disk Usage After Upgrading From Cassandra 3.
sstableexpiredblocker tool to check about this.
BR
MK
From: William Crowell via user
Sent: March 20, 2025 13:58
To: user@cassandra.apache.org
Cc: William Crowell ; Sartor Fabien (DIN)
; tasmaniede...@free.fr
Subject: Re: Increased Disk Usage After Upgrading From Cassandra 3.x.x to 4.1.3
Stephane and
leexpiredblocker tool to check about this. BR MK From: William
Crowell via user < user@cassandra.apache.org > Sent: March 20, 2025 13:58 To: user@cassandra.apache.org Cc: William Crowell < wcrow...@perforce.com >; Sartor Fabien (DIN) <
fabien.sar...@etat.ge.ch >; tasmaniede...@free.f
set to 0).
>
> This has occurred in some systems in past.
>
> You may use the sstableexpiredblocker tool to check about this.
>
>
>
> BR
>
> MK
>
>
>
> *From:* William Crowell via user
> *Sent:* March 20, 2025 13:58
> *To:* user@cassandra.apache.org
&g
ensions = {}
AND gc_grace_seconds = 864000
AND max_index_interval = 2048
AND memtable_flush_period_in_ms = 0
AND min_index_interval = 128
AND read_repair = 'BLOCKING'
AND speculative_retry = '99p';
*/
Regards,
William Crowell
From: Sartor Fabien (DIN) via us
*To: *user@cassandra.apache.org
*Cc: *William Crowell , Bowen Song
*Subject: *Re: Increased Disk Usage After Upgrading From Cassandra
3.x.x to 4.1.3
Bowen,
This is just a single Cassandra node. Unfortunately, I cannot get on
the box at the moment, but the following configuration is in
To: user@cassandra.apache.org
Cc: William Crowell , Bowen Song
Subject: Re: Increased Disk Usage After Upgrading From Cassandra 3.x.x to 4.1.3
Bowen,
This is just a single Cassandra node. Unfortunately, I cannot get on the box
at the moment, but the following configuration is in cassandra.yaml
the command: find . -iname snapshots
-exec du -h {} \;
Best regards,
Fabien
De : William Crowell via user
Envoyé : vendredi, 14 mars 2025 10:51
À : user@cassandra.apache.org
Cc : William Crowell
Objet : Re: Increased Disk Usage After Upgrading From Cassandra 3.x.x to 4.1.3
PRUDENCE. Ce
user
Cc: Bowen Song
Subject: Re: Increased Disk Usage After Upgrading From Cassandra 3.x.x to 4.1.3
A few suspects:
* snapshots, which could've been created automatically, such as by dropping or
truncating tables when auto_snapshots is set to true, or compaction
A few suspects:
* snapshots, which could've been created automatically, such as by
dropping or truncating tables when auto_snapshots is set to true, or
compaction when snapshot_before_compaction is set to true
* backups, which could've been created automatically, e.g. when
incremental_backup
<mailto:user@cassandra.apache.org>
mailto:user@cassandra.apache.org>>
Cc: William Crowell mailto:wcrow...@perforce.com>>
Subject: Re: Increased Disk Usage After Upgrading From Cassandra 3.x.x to 4.1.3
You don't often get email from
luciano.grei...@gmail.com<mailto:luciano.
rowell mailto:wcrow...@perforce.com>>
Subject: Re: Increased Disk Usage After Upgrading From Cassandra 3.x.x to 4.1.3
You don't often get email from
luciano.grei...@gmail.com<mailto:luciano.grei...@gmail.com>. Learn why this is
important<https://aka.ms/LearnAboutSenderIdentification
@cassandra.apache.org
*Cc: *William Crowell
*Subject: *Re: Increased Disk Usage After Upgrading From Cassandra
3.x.x to 4.1.3
You don't often get email from luciano.grei...@gmail.com. Learn
why this is important <https://aka.ms/LearnAboutSenderIdenti
that would affect disk
> space?
>
>
>
> Thank you for your reply,
>
>
>
> William Crowell
>
>
>
> *From: *Luciano Greiner
> *Date: *Thursday, March 13, 2025 at 10:21 PM
> *To: *user@cassandra.apache.org
> *Cc: *William Crowell
> *Subject: *Re:
@cassandra.apache.org
Cc: William Crowell
Subject: Re: Increased Disk Usage After Upgrading From Cassandra 3.x.x to 4.1.3
You don't often get email from luciano.grei...@gmail.com. Learn why this is
important<https://aka.ms/LearnAboutSenderIdentification>
Haven't you forgot to clean some snap
am Crowell via user
> *Date: *Wednesday, March 12, 2025 at 4:42 PM
> *To: *user@cassandra.apache.org
> *Cc: *William Crowell
> *Subject: *Re: Increased Disk Usage After Upgrading From Cassandra 3.x.x
> to 4.1.3
>
> I also forgot to include we do compaction once a week.
>
>
Hi,
Is this mailing list still active?
Thanks.
From: William Crowell via user
Date: Wednesday, March 12, 2025 at 4:42 PM
To: user@cassandra.apache.org
Cc: William Crowell
Subject: Re: Increased Disk Usage After Upgrading From Cassandra 3.x.x to 4.1.3
I also forgot to include we do compaction
I also forgot to include we do compaction once a week.
Hi. A few months ago, I upgraded a single node Cassandra instance from version
3 to 4.1.3. This instance is not very large with about 15 to 20 gigabytes of
data on version 3, but after the update it has went substantially up to over
100gb
22 matches
Mail list logo
