Reduce GCGraceSeconds in storage.conf, that should work.
On Tue, May 4, 2010 at 2:31 PM, vineet daniel <[email protected]>wrote: > Only major compactions can clean out obsolete tombstones. > > On Tue, May 4, 2010 at 9:59 AM, Jonathan Ellis <[email protected]> wrote: > >> On Mon, May 3, 2010 at 8:45 PM, Kauzki Aranami <[email protected]> >> wrote: >> > Let me rephrase my question. >> > >> > How does Cassandra deal with bloom filter's false positives on deleted >> records? >> >> The same way it deals with tombstones that it encounters otherwise >> (part of a row slice, or in a memtable). >> >> All the bloom filter does is keep you from having to check rows that >> don't have any data at all for a given key. Tombstones are not the >> same as "no data at all," we do need to propagate tombstones during >> replication. >> >> -- >> Jonathan Ellis >> Project Chair, Apache Cassandra >> co-founder of Riptano, the source for professional Cassandra support >> http://riptano.com >> > >
