Deleting the commitlog files is harmless. It's just a tool that tries to keep Cassandra more in-sync with the other nodes. A standard repair will fix all problems that a commitlog replay might do too.

Best regards, 

Robin Verlangen
Software engineer


Disclaimer: The information contained in this message and attachments is intended solely for the attention and use of the named addressee and may be confidential. If you are not the intended recipient, you are reminded that the information remains the property of the sender. You must not use, disclose, distribute, copy, print or rely on this e-mail. If you have received this message in error, please contact the sender immediately and irrevocably delete this message and any copies.

2012/9/8 Rene Kochen <>
OK, thanks! I will vote for that ticket.

On a production system, I have an extremely big table. I want to physically delete it. It it safe to just delete the commit log files after a drain?

1) Drain node
2) Stop Cassandra
3) Delete commit log files
4) Delete all files related to the big table
5) Restart Cassandra



2012/9/7 Rob Coli <>
On Fri, Sep 7, 2012 at 6:38 AM, Rene Kochen <> wrote:
> If I use node-tool drain, it does stop accepting writes and flushes the
> tables. However, is it normal that the commit log files are not deleted and
> that it gets replayed?

It's not expected by design, but it does seem to be normal in
cassandra 1.0.x. I've spoken with other operators and they anecdotally
report the same behavior when doing the same operation you describe.

The more people who report that they have the issue, the greater
chance of a response or fix, so I suggest commenting "me too!" on that
ticket.. :)


=Robert Coli
YAHOO - rcoli.palominob
SKYPE - rcoli_palominodb