Elasticsearch supports a timeout parameter. At the same time, Console configures requests with the elasticsearch.requestTimeout defined in kibana.yml. If the latter is shorter than the former, then requests sent in Console can time out unexpectedly. This behavior creates a discrepancy with the behavior of an identical request sent through cURL, which isn't subject to the elasticsearch.requestTimeout setting, and so won't time out.
Solution
We can solve this by checking if there's a timeout parameter set in the request, compare it to the value set in elasticsearch.requestTimeout, and configure the request to use the greater value of the two.
Problem
Elasticsearch supports a
timeout
parameter. At the same time, Console configures requests with theelasticsearch.requestTimeout
defined inkibana.yml
. If the latter is shorter than the former, then requests sent in Console can time out unexpectedly. This behavior creates a discrepancy with the behavior of an identical request sent through cURL, which isn't subject to theelasticsearch.requestTimeout
setting, and so won't time out.Solution
We can solve this by checking if there's a
timeout
parameter set in the request, compare it to the value set inelasticsearch.requestTimeout
, and configure the request to use the greater value of the two.