I don't think it works like that. clearsnapshot --all would remove all snapshots. Here is an example:
$ 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 --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/snapshots/: No such file or directory $ On Thu, Apr 30, 2020 at 5:44 PM Erick Ramirez <erick.rami...@datastax.com> wrote: > 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 hopefully provide a user-friendlier > solution. Cheers! >
