cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kallin Nagelberg <kallin.nagelb...@gmail.com>
Subject Re: time to live rows
Date Mon, 14 Feb 2011 16:40:38 GMT
Huh... I usually insert, compact, then flush. Apparently I've been
doing it wrong my whole life. So it needs like a courtesy flush. Let
me try that :)

-Kal

On Thu, Feb 10, 2011 at 3:06 AM, Sylvain Lebresne <sylvain@datastax.com> wrote:
> Kal, you may have to flush before compacting.
> If you insert then compact, then it's almost certain that the inserts
> are still in the memtable, and thus not compacted.
> On Tue, Feb 8, 2011 at 9:54 PM, Kallin Nagelberg
> <kallin.nagelberg@gmail.com> wrote:
>>
>> What's the secret recipe that I'm missing? I tried forcing compaction
>> on my column family's JMX bean
>> (org.apache.cassandra.db.ColumnFamilies.Main.Session) in jconsole,
>> after gc_grace had passed (i set it to 60).
>>
>> Thanks,
>> -Kal
>>
>> On Tue, Feb 8, 2011 at 3:46 PM, Benjamin Coverston
>> <ben.coverston@datastax.com> wrote:
>> >
>> > On 2/8/11 1:23 PM, Kallin Nagelberg wrote:
>> >>
>> >> I did read those articles, but I didn't know know that deleting all
>> >> the columns on a row was equivalent to deleting the row. Like I
>> >> mentioned, I did delete all the columns from all my rows and then
>> >> forced compaction before and after gc_grace had passed, but all the
>> >> rows still exist. If they never disappear, then won't I run out of
>> >> resources eventually?
>> >>
>> >> -Kal
>> >
>> > You would, if there weren't a way to get rid of tombstones:
>> >
>> > http://wiki.apache.org/cassandra/DistributedDeletes
>> >
>> > --
>> > Ben Coverston
>> > DataStax -- The Apache Cassandra Company
>> >
>> >
>
>

Mime
View raw message