A newer version is available. For the latest information, see the
current release documentation.
timeout_override
edittimeout_override
editThis 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: ...
Actions snapshot, restore, and
forcemerge will override this value to 21600
if
timeout_override
is unset. The close action will override the
value to 180 if unset.
Some actions have a default value for timeout_override
. The following table
shows these default values:
Action Name | Default timeout_override Value |
---|---|
|
180 |
|
21600 |
|
21600 |
|
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.