> I thought that the snapshot size was not counted in the load.
>
That's correct. I suggested looking at what nodetool tablestats reports so
you can compare that against du/df outputs for clues as to why there is
such a large discrepancy. Cheers!
-
The amount of file system data under the cassandra data directory after
excluding all content in the snapshots subdirectories. Because all SSTable
data files are included, any data that is not cleaned up, such as
TTL-expired cell or tombstoned data) is counted.
Thanks, Erick!
I thought that the snapshot size was not counted in the load.
Il giorno lun 3 feb 2020 alle ore 23:24 Erick Ramirez
ha scritto:
> Why the df -h and du -sh shows a big discrepancy? nodetool load is it
>> computed with df -h?
>>
>
> In Linux terms, df reports the filesystem disk
>
> Why the df -h and du -sh shows a big discrepancy? nodetool load is it
> computed with df -h?
>
In Linux terms, df reports the filesystem disk usage while du is an
*estimate* of the file space usage. What that means is that the operating
system uses different accounting between the two
Hello!
I was trying to understand the below differences:
Cassandra 3.11.4
i3xlarge aws nodes
$ du -sh /mnt
123G/mnt
$ nodetool info
ID : 3647fcca-688a-4851-ab15-df36819910f4
Gossip active : true
Thrift active : true
Native Transport active: true
Load
