You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user@cassandra.apache.org by Dan Larsen <da...@techba.se> on 2009/10/08 10:55:04 UTC

Quick nodeprobe question

Every time cassandra does a flush, the dbs grows, but nothing happens  
to the commitlog

Am I missing something?
Isn't the commitlog suppose to get truncated at some point?
Is there a way to flush the commitlog to the dbs and truncate the  
commitlog?
I have tried pushing the forceflush() from the jconsole ui, but the  
commitlog still doesn't get truncated...

Thanks!
Dan

Re: Quick nodeprobe question

Posted by Dan Larsen <da...@techba.se>.

Awesome! :-)

Thanks!

On 08/10/2009, at 15.25, Jonathan Ellis wrote:

> This is fixed in the 0.4 branch and will be included in a forthcoming
> 0.4.1 release.
>
> On Thu, Oct 8, 2009 at 3:55 AM, Dan Larsen <da...@techba.se> wrote:
>> Every time cassandra does a flush, the dbs grows, but nothing  
>> happens to the
>> commitlog
>>
>> Am I missing something?
>> Isn't the commitlog suppose to get truncated at some point?
>> Is there a way to flush the commitlog to the dbs and truncate the  
>> commitlog?
>> I have tried pushing the forceflush() from the jconsole ui, but the
>> commitlog still doesn't get truncated...
>>
>> Thanks!
>> Dan
>>
>

Re: Quick nodeprobe question

Posted by Jonathan Ellis <jb...@gmail.com>.

This is fixed in the 0.4 branch and will be included in a forthcoming
0.4.1 release.

On Thu, Oct 8, 2009 at 3:55 AM, Dan Larsen <da...@techba.se> wrote:
> Every time cassandra does a flush, the dbs grows, but nothing happens to the
> commitlog
>
> Am I missing something?
> Isn't the commitlog suppose to get truncated at some point?
> Is there a way to flush the commitlog to the dbs and truncate the commitlog?
> I have tried pushing the forceflush() from the jconsole ui, but the
> commitlog still doesn't get truncated...
>
> Thanks!
> Dan
>