We are designing our cluster taking into consideration some Elasticsearch best practices, focusing on keeping the shard size as close to our desired one (currently 25gb) as possible.
We decided to create ILM policies in order to achieve that, by rolling the indices using
max_age to simplify the index management. However, age rotation may lead to smaller indices.
The shrink action would be a good choice in this case, but handling it with ILM seems to have certain limitations since the only setting available is
It would be more convenient to shrink the indices taking into account the index primary shards and its size since we can not know in advance which number of shards will be accurate.
Is there any feature that might allow us to achieve this? Can it be approached differently?
I would appreciate any help.