Hi Andreas, So does that mean it can compact the 'hottest' partitions into a new sstable but the old sstables may not immediately be removed so the same data could be in more that one sstable? That would certainly explain the difference we see when we manually run nodetool compact.
Thanks Phil Andreas Finke wrote > Hi Phil, > > I found an interesting blog entry that may address your problem. > > http://www.datastax.com/dev/blog/optimizations-around-cold-sstables > > It seems that compaction is skipped for stables which so mit satisfy a > certain read rate. Please check. > > > Kind regards > > Andreas Finke > Java Developer > Solvians IT-Solutions GmbH > > > ---- Phil Luckhurst wrote ---- > > Definitely no TTL and records are only written once with no deletions. > > Phil > > > DuyHai Doan wrote >> Are you sure there is no TTL set on your data? It might explain the >> shrink >> in sstable size after compaction. > > > > > > -- > View this message in context: > http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Can-SSTables-overlap-with-SizeTieredCompactionStrategy-tp7594574p7594644.html > Sent from the > cassandra-user@.apache > mailing list archive at Nabble.com. -- View this message in context: http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Can-SSTables-overlap-with-SizeTieredCompactionStrategy-tp7594574p7594658.html Sent from the cassandra-u...@incubator.apache.org mailing list archive at Nabble.com.
