timeout_override

edit

This setting is available in all actions.

action: forcemerge
description: >-
  Perform a forceMerge on selected indices to 'max_num_segments' per shard
options:
  max_num_segments: 2
  timeout_override: 21600
filters:
- filtertype: ...

If timeout_override is unset in your configuration, some actions will try to set a sane default value.

The following table shows these default values:

Action Name Default timeout_override Value

close

180

delete_snapshots

300

forcemerge

21600

restore

21600

snapshot

21600

All other actions have no default value for timeout_override.

This setting must be an integer number of seconds, or an error will result.

This setting is particularly useful for the forceMerge action, as all other actions have a new polling behavior when using wait_for_completion that should reduce or prevent client timeouts.