Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (athena.apache.org: domain of hsiao.chuanheng@gmail.com
 designates 209.85.219.44 as permitted sender)
MIME-Version: 1.0
From: Chuan-Heng Hsiao <hsiao.chuanheng@gmail.com>
Date: Sat, 17 Nov 2012 09:30:48 +0800
Message-ID: 
 <CAE9BFj_6p2mJpM3tKWVz+3ibm+WCrZJn8Kfp3K7z--D0Yh2D1A@mail.gmail.com>
Subject: huge commitlog
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1

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