incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chuan-Heng Hsiao <hsiao.chuanh...@gmail.com>
Subject huge commitlog
Date Sat, 17 Nov 2012 01:30:48 GMT
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