cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aaron Morton <>
Subject Re: commitlogs not draining
Date Thu, 07 Jul 2011 02:17:26 GMT
When you run drain the node will log someone like "node drained" when it is done.

The commit log should be empty, any data in the log may be due to changes in the system tables
after the drain. Can you raise a ticket and include the commit logs left behind and any relevant
log messages?

The non draining logs may be this .

If a node tool flush does not clear them a restart will.


Aaron Morton
Freelance Cassandra Developer

On 7/07/2011, at 12:26 PM, Scott Dworkis <> wrote:

> couple questions about commitlogs and the nodetool drain operator:
> * in 0.6, after invoking a drain, the commitlog directory would be empty. in 0.8, it
seems to contain 2 files, a 44 byte .header file and 270 byte .log file.  do these indicate
a fully drained commitlog?
> * i have a couple nodes for which the commitlogs do not seem to be draining at all...
they remain several hundred k or meg in size.  are they corrupt? if the data is not precious,
is there some way to clear and reset them to work around this?
> also, i see this in system.log:
> /data/var/log/cassandra/system.log.1:DEBUG [COMMIT-LOG-WRITER] 2011-07-06 11:04:10,076 (line 473) Not safe to delete commit log CommitLogSegment(/data/var/lib/cassandra/commitlog/CommitLog-1309288064262.log);
dirty is LocationInfo (0), ; hasNext: true
> -scott

View raw message