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 disk space.
Hope this helps. Carlos Alonso | Software Engineer | @calonso <https://twitter.com/calonso> On 22 March 2016 at 07:57, Anishek Agarwal <[email protected]> wrote: > 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 ? > > Thanks In Advance. > Anishek >
