Re: C* 3.5 - Not all SSTables were removed in DTCS

bug for this behaviour? Why one node removed *all* data at once (there's data that should expire 3 months ago) while others not? All nodes are equal in spec and configuration. -Jacek 2016-12-08 14:11 GMT+01:00 Jacek Luczak <difrost.ker...@gmail.com>: > Fellow C* users, > > I'v

C* 3.5 - Not all SSTables were removed in DTCS

Fellow C* users, I've got a cluster of C* 3.5 serving a single keyspace with DTCS table and no deletes. We knew that data does not expire on time (even after gc_grace_period) - that's sth we wanted to investigate later and eventually let C* to keep it longer. The moment when C* decided to remove

Re: Upgredesstables doing 4K reads

> Alain Rodriguez - al...@thelastpickle.com > France > > The Last Pickle - Apache Cassandra Consulting > http://www.thelastpickle.com > > > > 2016-06-02 13:43 GMT+02:00 Jacek Luczak <difrost.ker...@gmail.com>: >> >> Hi, >> >> I've got a 6 node C*

Upgredesstables doing 4K reads

Hi, I've got a 6 node C* cluster (all nodes are equal both in OS and HW setup, they are DL380 Gen9 with Smart Array RAID 50,3 on SAS 15K HDDs) which has been recently updated from 2.2.5 to 3.5. As part of the update I've done the upgradesstables. On 4 nodes the average request size issued to the