cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From aaron morton <>
Subject Re: 1.1 not removing commit log files?
Date Mon, 04 Jun 2012 18:14:53 GMT
Apply the local hint mutation follows the same code path and regular mutations. 

When the commit log is being truncated you should see flush activity, logged from the ColumnFamilyStore
with "Enqueuing flush of " messages. 

If you set DEBUG logging for the  org.apache.cassandra.db.ColumnFamilyStore it will log if
it things the CF is clean and no flush takes place. 

If you set DEBUG logging on org.apache.cassandra.db.commitlog.CommitLog we will see if the
commit log file could not be deleted because a dirty CF was not flushed. 


Aaron Morton
Freelance Developer

On 2/06/2012, at 4:43 AM, Rob Coli wrote:

> On Thu, May 31, 2012 at 7:01 PM, aaron morton <> wrote:
>> But that talks about segments not being cleared at startup. Does not explain
>> why they were allowed to get past the limit in the first place.
> Perhaps the commit log size tracking for this limit does not, for some
> reason, track hints? This seems like the obvious answer given the
> state which appears to trigger it? This doesn't explain why the files
> aren't getting deleted after the hints are delivered, of course...
> =Rob
> -- 
> =Robert Coli
> YAHOO - rcoli.palominob
> SKYPE - rcoli_palominodb

View raw message