Re: Nodetool clearsnapshot does not delete snapshot for dropped column_family

2020-04-30 Thread Sebastian Estevez
7631a60bb0/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 >> >> Requeste

Re: Nodetool clearsnapshot does not delete snapshot for dropped column_family

2020-04-30 Thread Sergio
e: > > $ 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 clearsnap

Re: Nodetool clearsnapshot does not delete snapshot for dropped column_family

2020-04-30 Thread Nitan Kainth
andra 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-5bf825428b3811eabe0c6b7631a

Re: Nodetool clearsnapshot does not delete snapshot for dropped column_family

2020-04-30 Thread Erick Ramirez
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 or

Nodetool clearsnapshot does not delete snapshot for dropped column_family

2020-04-30 Thread Sergio Bilello
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? Thank

nodetool clearsnapshot -t 1537185517560-rmsharesducc

2018-09-27 Thread Lou DeGenaro
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:~> /users1/degenaro/svn/apache/ducc/workspace-trunk/cassandra

Re: Nodetool clearsnapshot doesn't support Column Families

2016-05-18 Thread Dominik Keil
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, > > > >

Nodetool clearsnapshot doesn't support Column Families

2016-05-17 Thread Anubhav Kale
Hello, I noticed that clearsnapshot doesn't support removing snapshots on a per CF, like how snapshots lets you take it per CF. http://docs.datastax.com/en/cassandra/2.1/cassandra/tools/toolsClearSnapShot.html I couldn't find a JIRA to address this. Is this intentional ? If so, I am curious to

Re: Nodetool clearsnapshot

2015-01-13 Thread Batranut Bogdan
: > 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

Re: Nodetool clearsnapshot

2015-01-13 Thread Yuki Morishita
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 > wrote: > > > Hi, > > I have read that snapshots are basicaly symli

Re: Nodetool clearsnapshot

2015-01-13 Thread Batranut Bogdan
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 wrote: Hi

Re: Nodetool clearsnapshot

2015-01-13 Thread Jan Kesten
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. This

Nodetool clearsnapshot

2015-01-13 Thread Batranut Bogdan
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...

Re: Issue with nodetool clearsnapshot

2012-03-06 Thread B R
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 wrote: > 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 ? > >

Re: Issue with nodetool clearsnapshot

2012-03-06 Thread aaron morton
> 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 witho

Re: Issue with nodetool clearsnapshot

2012-03-05 Thread B R
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 Standard1-g-7968-Compact

Re: Issue with nodetool clearsnapshot

2012-03-05 Thread aaron morton
> 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 th

Issue with nodetool clearsnapshot

2012-03-05 Thread B R
Version 0.8.9 We run a 2 node cluster with RF=2. We ran a scrub and after that ran the clearsnapshot to remove the backup snapshot created by scrub. It seems that instead of removing the snapshot, clearsnapshot moved the data files from the snapshot directory to the parent directory and the size o