Sorry for the late reply.
To immediately solve the problem you can restart Cassandra and all the open
file descriptors to the deleted snapshots should disappear.
As for why it happened I would first address the disk space issue and see
if the snapshot errors + open file descriptors issue still
On Mon, Mar 16, 2015 at 6:51 PM, Ben Bromhead b...@instaclustr.com wrote:
If you are running a sequential repair (or have previously run a sequential
repair that is still running) Cassandra will still have the file descriptors
open for files in the snapshot it is using for the repair operation.
If you are running a sequential repair (or have previously run a sequential
repair that is still running) Cassandra will still have the file
descriptors open for files in the snapshot it is using for the repair
operation.
From the http://www.datastax.com/dev/blog/repair-in-cassandra
*Cassandra
On Mon, Mar 16, 2015 at 5:28 PM, Jan cne...@yahoo.com wrote:
David;
all the packaged installations use the /var/lib/cassandra directory.
Could you check your yaml config files and see if you are using this default
directory for backups
May want to change it to a location with more disk
Cassandra will by default snapshot your data directory on the following
events:
- TRUNCATE and DROP schema events
- when you run nodetool repair
- when you run nodetool snapshot
Snapshots are just hardlinks to existing SSTables so the only disk space
they take up is for files that have
On Mon, Mar 16, 2015 at 6:12 PM, Ben Bromhead b...@instaclustr.com wrote:
Cassandra will by default snapshot your data directory on the following
events:
TRUNCATE and DROP schema events
when you run nodetool repair
when you run nodetool snapshot
Snapshots are just hardlinks to existing
