The following article has some good information for what you describe: http://www.datastax.com/dev/blog/optimizations-around-cold-sstables
Some related tickets which will provide background: https://issues.apache.org/jira/browse/CASSANDRA-5228 https://issues.apache.org/jira/browse/CASSANDRA-5515 On Tue, May 6, 2014 at 7:55 PM, Kevin Burton <bur...@spinn3r.com> wrote: > I'm looking at storing log data in Cassandra… > > Every record is a unique timestamp for the key, and then the log line for > the value. > > I think it would be best to just disable compactions. > > - there will never be any deletes. > > - all the data will be accessed in time range (probably partitioned > randomly) and sequentially. > > So every time a memtable flushes, we will just keep that SSTable forever. > > Compacting the data is kind of redundant in this situation. > > I was thinking the best strategy is to use setcompactionthreshold and set > the value VERY high to compactions are never triggered. > > Also, It would be IDEAL to be able to tell cassandra to just drop a full > SSTable so that I can truncate older data without having to do a major > compaction and without having to mark everything with a tombstone. Is this > possible? > > > > -- > > Founder/CEO Spinn3r.com > Location: *San Francisco, CA* > Skype: *burtonator* > blog: http://burtonator.wordpress.com > … or check out my Google+ > profile<https://plus.google.com/102718274791889610666/posts> > <http://spinn3r.com> > War is peace. Freedom is slavery. Ignorance is strength. Corporations are > people. > > -- ----------------- Nate McCall Austin, TX @zznate Co-Founder & Sr. Technical Consultant Apache Cassandra Consulting http://www.thelastpickle.com
