On Tue, Jun 19, 2012 at 2:30 PM, Edward Capriolo <edlinuxg...@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
