[BUG] 2.18-2.19.1: search node reported free space is not correct

[sandervandegeijn]

Describe the bug

Look at this screenshot:

Relevant config:

Related component

Storage

To Reproduce

We are running this on Kubernetes, disks are exposed correctly.

Expected behavior

Free space is consistent with the df -h output

Additional Details

Plugins
S3

Screenshots
See ^^

Host/Environment (please complete the following information):

• Docker image 2.19.1 on kubernetes

Additional context

[bugmakerrrrrr]

@sandervandegeijn the free space of search node does not include the space reserved for file cache

[sandervandegeijn]

Hm, then the 15GB difference is the metadata from the snapshot indices? Maybe we should document this, this is not currently in the docs. I'll create a PR if my assumption is correct.

[bugmakerrrrrr]

Hm, then the 15GB difference is the metadata from the snapshot indices?

AFAIK, the size of the metadata is very small, and the difference you're talking about could come from reserved space in the file system or other unrelated files (if any).