I am looking into freezing some of the indices in our cluster. Is there a way to freeze only specific range of indices? For example, those that are earlier than 2019. I tried to use freeze with range query but ended up freezing every index under, for example, metricbeat-*.
I am running into a similar situation with forcemerge. Is it possible to forcemerge only those indices that I am planning to freeze?
Than you for your quick reply @Yogesh_Gaikwad. I was not aware of the ILM.
It seems like if the policy is attached to each index one by one from the Index Management page, it is only then the policy starts working.
There are also strict rules around if you are using a rollover. I mostly was wanting to use this for Beats indices and the trick is to set the policy with rollover turned off.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.