I have enabled forcemerge management via curator and it is causing us an issue. That is, after enabling it late on Thursday we now have 1400+ running tasks. This is not a large cluster and so is causing widespread issues.
Config file looks like this:
action_forcemerge.yml: |- --- actions: 1: action: forcemerge description: "Perform forcemerge operation on rolled indices" options: max_num_segments: 1 timeout_override: 21600 ignore_empty_list: true delay: 300 disable_action: true filters: - filtertype: age source: creation_date direction: older unit: days unit_count: 1 - filtertype: forcemerged max_num_segments: 1 exclude: true
It's triggered from a cronjob which runs once per day...
However, the tasks that are running are not cancellable. So, how can I clear them down? They don't seem to be active in that segment counts have not fallen to 1 per shard with 4 merges currently running against today's index (1 per shard).