I was exactly in your same situation, I could only reclaim disk space for trimmed data this way:
very low gc_grace + size tiered compaction + slice timestamp deletes + major compaction 2014-08-18 12:06 GMT+02:00 Rahul Neelakantan <ra...@rahul.be>: > Is that GC_grace 300 days? > > Rahul Neelakantan > > > On Aug 18, 2014, at 5:51 AM, Dimetrio <dimet...@flysoft.ru> wrote: > > > > In our Twitter-like application users have their own timelines with news > from > > subscriptions. To populate timelines we're using fanout on write. But we > > forced to trim it to keep free disk space under control. > > > > We use wide rows pattern and trim them with "DELETE by primary key USING > > TIMESTAMP". But it seems our efforts have no effect and disk free space > > decreases rapidly, even after compaction. > > > > It is clear for us that it's not the best use case for Cassandra, but > maybe > > there is a way to decrease disk utilisation for this pattern? > > > > Our cluster consists of 15 c3.4xlarge nodes with 300 GB storage. > Timeline's > > files take up 170 GB on each node. > > gc_grace is 300, > > rf=3 > > > > > > > > -- > > View this message in context: > http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/disk-space-and-tombstones-tp7596356.html > > Sent from the cassandra-u...@incubator.apache.org mailing list archive > at Nabble.com. >
