Kibana search.defaultTimeout: missing upper bound and disconnect handling

Kibana Search Timeout Configuration

The search.defaultTimeout setting in kibana.yml controls how long Kibana will allow a search request to run before aborting it. The default is 30 seconds.

Missing Upper Bound

Documentation does not specify a maximum value for this parameter. Administrators can set arbitrarily high values, but the impact on cluster resources and error reporting latency is unclear.

Client Disconnect Behavior

When a user closes the browser tab or otherwise disconnects, Kibana does not automatically cancel the in‑progress search on the server side. The request continues until it reaches the configured timeout or completes.

Unresolved Questions

• What is the recommended upper limit for search.defaultTimeout to balance query performance and resource consumption?
• Is there a built‑in mechanism or best practice to terminate server‑side searches when the client disconnects?
• How can administrators monitor and mitigate prolonged resource usage caused by excessively long timeout values?