Re: Strange row expiration behavior

2012-10-24 Thread Stephen Mullins
That worked perfectly, inserting another row after the first compaction, then flushing and compacting again triggered the empty rows to be removed. Thanks for your help and for clarifying the "gcBefore" point Aaron. Stephen On Tue, Oct 23, 2012 at 4:47 PM, aaron morton wrote: > In the first exam

Re: Strange row expiration behavior

2012-10-23 Thread aaron morton
> In the first example, I am running compaction at step 7 through nodetool, Sorry missed that. >> insert a couple rows with ttl=5 (again, just a small number) >> ExpiringColumn's are only purged if their TTL has expired AND their absolute (node local) expiry time occurred before the current "g

Re: Strange row expiration behavior

2012-10-23 Thread Stephen Mullins
Thanks Aaron, my reply is inline below: On Tue, Oct 23, 2012 at 2:38 AM, aaron morton wrote: > Performing these steps results in the rows still being present using > *cassandra-cli > list*. > > I assume you are saying the row key is listed without any columns. aka a > ghost row. > Correct. > >

Re: Strange row expiration behavior

2012-10-23 Thread aaron morton
> Performing these steps results in the rows still being present using > cassandra-cli list. I assume you are saying the row key is listed without any columns. aka a ghost row. > What gets really odd is if I add these steps it works That's working as designed. gc_grace_seconds does not spec