Hi Anishek
they were created from more than a couple of months ago
You then probably free a fair amount of data :-).
We didn't do any actions that would create a snapshot
You shouldn't have any snapshot unless you drop or truncate a table, call
them through "nodetool snapshot" or run repair
Thanks Carlos,
We didn't do any actions that would create a snapshot, and i couldn't find
the command in 2.0.17, but i found the respective snapshot directories and
they were created from more than a couple of months ago so, i it might be
that i might have forgotten, its fine now, i have cleared t
I'd say you have snapshots holding disk space.
Check it with nodetool listsnapshots. A snapshot is automatically taken on
destructive actions (drop, truncate...) and is basically a hard link to the
involved SSTables, so it's not considered as data load from Cassandra but
it is effectively using di
Hello,
Using cassandra 2.0.17 on one of the 7 nodes i see that the "Load" column
from nodetool status
shows around 279.34 GB where as doing df -h on the two mounted disks the
total is about 400GB any reason of why this difference could show up and
how do i go about finding the cause for this ?
T
