o:l...@lapo.it>
Sent: Friday, December 30, 2022 4:12 AM
To: mailto:user@cassandra.apache.org
Subject: [EXTERNAL] Re: Best compaction strategy for rarely used data
On 2022-12-29 21: 54, Durity, Sean R via user wrote: > At some point you will
end up with large sstables (like 1 TB) t
: [EXTERNAL] Re: Best compaction strategy for rarely used data
On 2022-12-29 21: 54, Durity, Sean R via user wrote: > At some point you will
end up with large sstables (like 1 TB) that won’t > compact because there are
not 4 similar-sized ones able to be compacted Yes, that's exa
On 2022-12-29 21:54, Durity, Sean R via user wrote:
At some point you will end up with large sstables (like 1 TB) that won’t
compact because there are not 4 similar-sized ones able to be compacted
Yes, that's exactly what's happening.
I'll see maybe just one more compaction, since the biggest
, December 29, 2022 4:51 AM
To: user@cassandra.apache.org
Subject: [EXTERNAL] Re: Best compaction strategy for rarely used data
Hi Lapo Take a look at TWCS, I think that could help your use case: https:
//thelastpickle. com/blog/2016/12/08/TWCS-part1. html [thelastpickle. com]
Regards Paul Chandler
Hi Lapo
Take a look at TWCS, I think that could help your use case:
https://thelastpickle.com/blog/2016/12/08/TWCS-part1.html
Regards
Paul Chandler
Sent from my iPhone
> On 29 Dec 2022, at 08:55, Lapo Luchini wrote:
>
> Hi, I have a table which gets (a lot of) data that is written once an
Hi, I have a table which gets (a lot of) data that is written once and
very rarely read (it is used for data that is mandatory for regulatory
reasons), and almost never deleted.
I'm using the default SCTS as at the time I didn't know any better, but
SSTables size are getting huge, which is a p
