Index clone v.s. ILM

Hello nice people of Elasticsearch,

what is the proper way to apply ILM to cloned indices?
I know I can set index.lifecycle.origination_date so ILM knows how old data is,
but that often causes the index to go through multiple relocations and force-merges.

I assume this is because ILM treats the cloned index as if it was new.
Is there a way to clone the ILM state along with the index, so this does not happen?

Thank you!

Currently I am using this workaround:

1 Like

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