gt; so, don’t try to get clever and set it to something very close to 99%, the
> estimated tombstone ratio isn’t that accurate)
>
>
>
> - Jeff
>
>
>
>
>
> *From: *Alain RODRIGUEZ <arodr...@gmail.com>
> *Reply-To: *"user@cassandra.apache.org" <user@cas
he
> estimated tombstone ratio isn’t that accurate)
>
>
>
> - Jeff
>
>
>
>
>
> *From: *Alain RODRIGUEZ <arodr...@gmail.com>
> *Reply-To: *"user@cassandra.apache.org" <user@cassandra.apache.org>
> *Date: *Monday, July 11, 2016 at 1:05 PM
> *To:
@Alain, @Jeff
Thank you very much for your time. I really appreciate it!
Yes I found many posts/hints about TWCS, definitely look very promising. I
understand correctly that I can swap compaction strategy without any major
concern, right?
About the read repair, Am I correct in thinking that the
o isn’t that accurate)
- Jeff
From: Alain RODRIGUEZ <arodr...@gmail.com>
Reply-To: "user@cassandra.apache.org" <user@cassandra.apache.org>
Date: Monday, July 11, 2016 at 1:05 PM
To: "user@cassandra.apache.org" <user@cassandra.apache.org>
Subject: Re
@Jeff
Rather than being an alternative, isn't your compaction strategy going to
deprecate (and finally replace) DTCS ? That was my understanding from the
ticket CASSANDRA-9666.
@Riccardo
If you are interested in TWCS from Jeff, I believe it has been introduced
in 3.0.8 actually, not 3.0.7
48 sstables isn’t unreasonable in a DTCS table. It will continue to grow over
time, but ideally data will expire as it nears your 90 day TTL and those tables
should start dropping away as they age.
3.0.7 introduces an alternative to DTCS you may find easier to use called TWCS.
It will
