This document looks good and is helpful for those who are setting up CCR for time series use cases. Thank you.
I have another scenario where full text search usecase-based indices:
eg indices: clientid_indexName_v2-20240807041326
These sorts of indices are created daily via the dotnet service when invoked via scheduler jobs.
Unfortunately,, this scheduled jobs gets killed abruptly if data loads are not finished before business start time, eg; 8AM
This means we can expect to have multiple indices in the cluster with the above-mentioned index pattern.
The good thing is that there is always one good index that has full data and aliases pointed to, and all the old indices are deleted post-full data load completion.
CCR Flow:
CCR auto-follow patterns are able to track these indices and replicate them in a follower cluster.
But old indices are not being cleaned up.
The idea is to set an ILM and clean up indices older than 10 days in the Follower cluster.
The document says it can be done automatically for rollover indices, but unfortunately, our indices are not set for rollover and are created daily.
Can this document be used to set unfollow on the older indices that are older than 10 days and set the delete phase via ILM?
Happy to hear the document is useful. From the article, index.lifecycle.indexing_complete and indexing_complete must be true on the leader index to succeed the unfollow.
Can this document be used to set unfollow on the older indices that are older than 10 days and set the delete phase via ILM?
As far as I know, there is no way to set unfollow in the ILM.
Can you check what are these values in leader index settings?
If the values are false you should find a way to make them true with a code or with ILM.
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.