My apologies for not being clear. What I meant was to run a du for every
subdirectory in the snapshots folder and compare them with the listsnapshots
output. As Kane pointed out, you might have subdirectories not listed as a
snapshot. Cheers!
>
The calculation isn't terribly smart - it simply sums up the size of all
the snapshots, which might not be accurate as multiple snapshots may point
to the same SSTable as they are hardlinks.
It really shouldn't be called TrueDiskSpaceUsed, but for some reason no one
is considering it a bug.
No problem. I'll use another node:
nodetool listsnapshots
Snapshot Details:
Snapshot name                           Â
Keyspace name Column family name True size Size on disk
truncated-1613059667093-extractedmetadata doc         Â
extractedmetadataÂ
>
> That said, the "Total TrueDiskSpaceUsed: 16.09 GiB" seems to be way off?
> Or is that value something else?
>
It's a bit late now since you've cleared them but it would have been good
to check the size of each snapshot directory with du and validate it
against the listsnapshots output.
FWIW
Ah - you are correct. auto_snapshot is set to true and there were
recent truncates and drops.
That said, the "Total TrueDiskSpaceUsed: 16.09 GiB" seems to be way
off? Or is that value something else?
Thank you!
-Joe
On 2/16/2021 4:46 PM, Arvinder Dhillon wrote:
You need to check if
You need to check if something/someone create snapshots.
Maybe your application drops and recreate tables, and "create snapshot
before drop" setting is enabled in your Cassandra setup?
-Arvi
On Tue, Feb 16, 2021, 1:04 PM Joe Obernberger
wrote:
> Hello all - I'm seeing a lot of disk usage by
Hello all - I'm seeing a lot of disk usage by snapshots. On this
particular node /data/1/cassandra, and /data/2/cassandra are the mount
points Cassandra is using for disk storage:
du -s -h /data/1/cassandra
211GÂ Â Â /data/1/cassandra
du -s -h /data/2/cassandra
343GÂ Â Â /data/2/cassandra
