Thanks for the response, Aaron.
Our usecase is, get the indices backed up in a local elk server and the delete the indices, it should automatically happen as well.
The Reindex Curator is just a trial as we don't want to run a curator with delete operations since things were not sure, as this is my first curator. I wanted to confirm that the curator which I wrote works and I didn't know that it will be such a long process, working with reindexing.
Once the curator started, is it possible that we know that the process got kicked off or something is happening, any logs or something that tells me that I have something running behind?
I was not sure about whether any regular ingest was happening but no, big reindex was definitely not happening.
Our cluster has 5 instances with 1 master node and 2 data nodes, rest one each for APM and Kibana.
We welcome with any of your suggestion
The rollover indices are not in our options since I dont want to risk it. Our data's are important, so we just want to back it up (elasticsearch-dump) and then delete them based on the request.
So I want to create a curator, which will first complete the backup/export and delete the indices.
One more thing, the curator(reindexing) is still running (for more than 27 hours)