Dropped (or truncated) Table (or keyspace) and Disk Space is not Reclaimed

This troubleshooting guide describes what to do when Scylla keeps using disk space after table or keyspaces are dropped or truncated.

Problem

When performing a DROP or TRUNCATE operation on a table or keyspace, disk usage is not seen to be reduced. Usually this is verified by using an external utility like du Linux command. This is caused by the fact that by default, Scylla creates a snapshot of every deleted table. Space won’t be reclaimed until the snapshot is deleted.

Solution

  1. Locate /var/lib/scylla/data/<your_keyspace>/<your_table>. Inside that directory you will see a snapshots subdirectory with your deleted data. Use the rm Linux utility to remove the files.
  2. If you are deleting an entire keyspace, repeat the procedure above for every table inside the keyspace.
  3. This behavior is controlled by the auto_snapshot flag in /etc/scylla/scylla.yaml, which set to true by default. To stop taking snapshots on deletion, set that flag to false and restart all your scylla nodes.

Troubleshoot