Re: How do TTLs generate tombstones

No it's never safe to set it to 0 as you'll disable hinted handoff for the table. If you are never doing updates and manual deletes and you always insert with a ttl you can get away with setting it to the hinted handoff period. On 6 Oct. 2017 1:28 am, "eugene miretsky"

LCS major compaction on 3.2+ on JBOD

Hi I am wondering how major compaction behaves for a table using LCS on JBOD with Cassandra 3.2+'s JBOD improvements. Up to then I know that major compaction would use a single thread, include all SSTables in a single compaction, and spit out a bunch of SSTables in appropriate levels. Does 3.2+

Calculate tokens from date range

We have data in tables with partitioning key as 'Timestamp' and we are in need of running repairs for last 3 months data because full repair is taking lot of time. We are migrating data from Cassandra version 2 to 3. Please guide us with your best suggestions. Thanks

[RELEASE] Apache Cassandra 2.2.11 released

The Cassandra team is pleased to announce the release of Apache Cassandra version 2.2.11. Apache Cassandra is a fully distributed database. It is the right choice when you need scalability and high availability without compromising performance. http://cassandra.apache.org/ Downloads of source

[RELEASE] Apache Cassandra 2.1.19 released

The Cassandra team is pleased to announce the release of Apache Cassandra version 2.1.19. Apache Cassandra is a fully distributed database. It is the right choice when you need scalability and high availability without compromising performance. http://cassandra.apache.org/ Downloads of source

Re: How do TTLs generate tombstones

Thanks Jeff, Make sense. If we never use updates (time series data), is it safe to set gc_grace_seconds=0. On Wed, Oct 4, 2017 at 5:59 PM, Jeff Jirsa wrote: > > The TTL'd cell is treated as a tombstone. gc_grace_seconds applies to > TTL'd cells, because even though the data

Re: table repair question

I'm doing it on a daily basis. If the repaired percentage drops from 80%, then I do a repair over that keyspace-table. Seems working fine for the last months without problems and avoids huge merkle tree building. No data loss so far. I'm running 3.11.0 btw. 2017-10-04 17:44 GMT-03:00 Blake

Re: CREATE INDEX without IF NOT EXISTS when snapshoting

Well, Patches submitted for version 3.0, 3.11 and trunk (although 3.0 patch can be applied to 3.11). Feel free to review and comment. Thanks! 2017-10-04 16:41 GMT-03:00 Javier Canillas : > Kurt, > > Thanks for your response. Created this ticket >

Re: Alter table gc_grace_seconds

Hi, On Wed, Oct 4, 2017 at 8:39 AM Oleksandr Shulgin < oleksandr.shul...@zalando.de> wrote: > If you have migrated ALL the data from the old CF, you could just use > TRUNCATE or DROP TABLE, followed by "nodetool clearsnapshot" to reclaim the > disk space (this step has to be done per-node). >