incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From aaron morton <aa...@thelastpickle.com>
Subject Re: huge commitlog
Date Sun, 18 Nov 2012 19:19:48 GMT
> I am wondering whether the huge commitlog size is the expected behavior or not?
Nope. 

Did you notice the large log size during or after the inserts ? 
If after did the size settle ?
Are you using commit log archiving ? (in commitlog_archiving.properties)

> and around 700 mini column family (around 10M in data_file_directories)
Can you describe how you created the 700 CF's ? 

> and how can we reduce the size of commitlog?
As a work around nodetool flush should checkpoint the log. 

Cheers

-----------------
Aaron Morton
Freelance Cassandra Developer
New Zealand

@aaronmorton
http://www.thelastpickle.com

On 17/11/2012, at 2:30 PM, Chuan-Heng Hsiao <hsiao.chuanheng@gmail.com> wrote:

> hi Cassandra Developers,
> 
> I am experiencing huge commitlog size (200+G) after inserting huge
> amount of data.
> It is a 4-node cluster with RF= 3, and currently each has 200+G commit
> log (so there are around 1T commit log in total)
> 
> The setting of commitlog_total_space_in_mb is default.
> 
> I am using 1.1.6.
> 
> I did not do nodetool cleanup and nodetool flush yet, but
> I did nodetool repair -pr for each column family.
> 
> There is 1 huge column family (around 68G in data_file_directories),
> and 18 mid-huge column family (around 1G in data_file_directories)
> and around 700 mini column family (around 10M in data_file_directories)
> 
> I am wondering whether the huge commitlog size is the expected behavior or not?
> and how can we reduce the size of commitlog?
> 
> Sincerely,
> Hsiao


Mime
View raw message