/snapshots/
>>
>> total 8
>>
>> drwxr-xr-x 2 cassandra cassandra 4096 Apr 30 23:17
>> dropped-1588288650821-a
>>
>> drwxr-xr-x 2 cassandra cassandra 4096 Apr 30 23:17 manual
>>
>> $ nodetool clearsnapshot --all
>>
>> Requested clearing
t;
> $ ls -l
> /ss/xx/cassandra/data/ww/a-5bf825428b3811eabe0c6b7631a60bb0/snapshots/
>
> total 8
>
> drwxr-xr-x 2 cassandra cassandra 4096 Apr 30 23:17 dropped-1588288650821-a
>
> drwxr-xr-x 2 cassandra cassandra 4096 Apr 30 23:17 manual
>
> $ nodetool clearsnapshot
cassandra 4096 Apr 30 23:17 manual
$ nodetool clearsnapshot --all
Requested clearing snapshot(s) for [all keyspaces] with [all snapshots]
$ ls -l
/ss/xx/cassandra/data/ww/a-5bf825428b3811eabe0c6b7631a60bb0/snapshots/
ls: cannot access
/ss/xx/cassandra/data/ww/a-5bf825428b3811eabe0c6b7631a60bb0
Yes, you're right. It doesn't show up in listsnapshots nor does
clearsnapshot remove the dropped snapshot because the table is no longer
managed by C* (because it got dropped). So you will need to manually remove
the dropped-* directories from the filesystem.
Someone here will either correct me
that removes the
column_family folder for each node.
I tried the nodetool clearsnapshot command but it didn't work and when I try to
nodetool listsnapshots I don't see anything. It is like hidden that space
occupied.
Any suggestion?
Thanks,
Sergio
Hello,
I issue the subject command running Cassandra 2.2.12 and get this response:
Requested clearing snapshot(s) for [all keyspaces] with snapshot name
[1537185517560-rmsharesducc]
But the snapshot does not go away.
degenaro@myhost1:~>
Hi,
Here's Cassandra's JIRA: https://issues.apache.org/jira/browse/CASSANDRA
As for your question: Yes, you can just rm -r a snapshot folder...
nothing bad will happen, except the deletion of that snapshot, obviously :-)
Regards
Am 17.05.2016 um 18:42 schrieb Anubhav Kale:
>
> Hello,
>
>
>
>
I have read that snapshots are basicaly symlinks and they do not take that much
space.Why if I run nodetool clearsnapshot it frees a lot of space? I am seeing
GBs freed...
Hi,
I have read that snapshots are basicaly symlinks and they do not take
that much space.
Why if I run nodetool clearsnapshot it frees a lot of space? I am
seeing GBs freed...
both together makes sense. Creating a snaphot just creates links for all
files unter the snapshot directory
OK Thanks,
But I also read that repair will take a snapshot. Due to the fact that I have
Replication factor 3 for my keyspace, I run nodetool clearsnapshot to keep disk
space use to a minimum. Will this impact my repair?
On Tuesday, January 13, 2015 4:19 PM, Jan Kesten j.kes
that I
have Replication factor 3 for my keyspace, I run nodetool clearsnapshot to
keep disk space use to a minimum. Will this impact my repair?
On Tuesday, January 13, 2015 4:19 PM, Jan Kesten j.kes...@enercast.de
wrote:
Hi,
I have read that snapshots are basicaly symlinks and they do
Bogdan batra...@yahoo.com wrote:
OK Thanks,
But I also read that repair will take a snapshot. Due to the fact that I
have Replication factor 3 for my keyspace, I run nodetool clearsnapshot to
keep disk space use to a minimum. Will this impact my repair?
On Tuesday, January 13, 2015 4:19 PM
1)Since you mentioned hard links, I would like to add that our data directory
itself is a sym-link. Could that be causing an issue ?
Seems unlikely.
I restarted the node and it went about deleting the files and the disk space
has been released. Can this be done using nodetool, and without
Thanks a lot, Aaron. Our cluster is much stable now. We'll look at
upgrading to 1.x in the coming weeks.
On Tue, Mar 6, 2012 at 2:33 PM, aaron morton aa...@thelastpickle.comwrote:
1)Since you mentioned hard links, I would like to add that our data
directory itself is a sym-link. Could that be
It seems that instead of removing the snapshot, clearsnapshot moved the data
files from the snapshot directory to the parent directory and the size of the
data for that keyspace has doubled.
That is not possible, there is only code there to delete a files in the
snapshot.
Note that in the
Hi Aaron,
1)Since you mentioned hard links, I would like to add that our data
directory itself is a sym-link. Could that be causing an issue ?
2)Yes, there are 0 byte files of the same numbers
in Keyspace1 directory
0 Mar 4 01:33 Standard1-g-7317-Compacted
0 Mar 3 22:58
16 matches
Mail list logo
