In ES 2.x, was it a bad idea to use the Force Merge API? I have found the danger alert only in the of the latest versions of ES docs.
In particular, this ES cluster is running version 2.4.4 and has a cron job that each night runs the following script:
- Search with the Scroll API on all indices all the documents with
_ttl< current time in ms
- Delete all the hits in the current Scroll via the Bulk API, repeat until the Scroll search does not return more hits
- Delete the scroll
index.ttl.disable_purgeto false, wait 20 minutes then set it to true
- Call the Force Merge API first with the parameters only_expunge_deletes=true&max_num_segments=20
, wait 5 minutes then call it again withmax_num_segments=20`.
This was set up by another person that previously managed the cluster, and I would like to know the implications of running the above script daily and if somehow can hinder the performance/health/disk usage of the cluster.
Thanks in advance.