On Sun, Sep 9, 2012 at 12:01 PM, Robin Verlangen wrote:
> 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.
This is not really true.. imagine
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*
*
*
W http://www.robinverlangen.nl
E ro...@us2
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)
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
cassand
Hi All,
I have a question about node-tool drain on a single Cassandra 1.0.11 node:
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?
Because if I do the following:
1) Write s
