ES Indexes significantly smaller than configured max

1. Describe your incident:

I was reviewing our indices to see if there were any adjustments needing to be made, and I noticed that many indexes are quite smaller than the configured maximum for the set, some on the scale of half as big. Here are two examples:

I understand that the sizes are supposed to be in the ballpark of the configured max, but these sizes are noticeably smaller than what I would expect. Is there another factor playing into these sizes that I haven’t learned about yet?

2. Describe your environment:

  • OS Information: Rocky Linux 8.7

  • Package Version: 4.3.9

  • Service logs, configurations, and environment variables:

3. What steps have you already taken to try and solve the problem?

Web searching, but I haven’t found resources that seem to apply to this.

4. How can the community help?

Just a simple explanation, or a link to a resource explaining why they might be this much smaller.

Rotation is based on the size of the index as reported by ES/OS stats API, which is the uncompressed size.
The numbers shown on the UI are the storage size on disk, after compression.

3 Likes

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