Index size mismatch in Kibana and linux console

Elastic Stack Elasticsearch
1

I am using Elasticsearch 6.3.2 to index a bunch of log file which are around 1.8 to 2 GB in size. The disk size shown in Kibana are close the expected size (size of input) but a du -sh on the data folder via the console shows a growth of around 5 to 7 GB for each of the input file.

Kindly help me understand if this is an expected behaviour or there is something wrong about it?

1 Like
2

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.