cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Spriegel (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3710) Add a configuration option to disable snapshots
Date Fri, 27 Jan 2012 01:24:39 GMT


Christian Spriegel commented on CASSANDRA-3710:

Update on my testsuite: I was just able to get jna running in my junits, therefore truncate
is finally working, which is good.

Unfortunetaly the performance of my testsuite is not good any more. It now took 25 minutes
instead of 3 minutes to run all my tests. The hard disk was busy all the time (top showed
~10% io wait).
I checked for snapshots in the cassandra directory: There were about 2300 folders within the
snapshots directory. Within these were ~30k files in all those directories. I assume that
the performance decrease is due to the 30k symlinks being created.
> Add a configuration option to disable snapshots
> -----------------------------------------------
>                 Key: CASSANDRA-3710
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>            Reporter: Brandon Williams
>             Fix For: 1.0.8
> Let me first say, I hate this idea.  It gives cassandra the ability to permanently delete
data at a large scale without any means of recovery.  However, I've seen this requested multiple
times, and it is in fact useful in some scenarios, such as when your application is using
an embedded cassandra instance for testing and need to truncate, which without JNA will timeout
more often than not.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message