incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonathan Ellis <jbel...@gmail.com>
Subject Re: Rules for Major Compaction
Date Wed, 20 Jun 2012 00:49:56 GMT
On Tue, Jun 19, 2012 at 2:30 PM, Edward Capriolo <edlinuxguru@gmail.com> wrote:
> You final two sentences are good ground rules. In our case we have
> some column families that have high churn, for example a gc_grace
> period of 4 days but the data is re-written completely every day.
> Write activity over time will eventually cause tombstone removal but
> we can expedite the process by forcing a major at night. Because the
> tables are not really growing the **warning** below does not apply.

Note that Cassandra 1.2 will automatically compact sstables that have
more than a configurable amount of expired data (default 20%).  So you
won't have to force a major for this use case anymore.

-- 
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com

Mime
View raw message