# elasticsearch.requestTimeout config setting being ignored by visualisations

**URL:** <https://discuss.elastic.co/t/elasticsearch-requesttimeout-config-setting-being-ignored-by-visualisations/166549>\
**Category:** Kibana\
**Created:** [January 31, 2019, 12:22pm UTC](https://discuss.elastic.co/t/elasticsearch-requesttimeout-config-setting-being-ignored-by-visualisations/166549 "2019-01-31T12:22:08Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![jong99](https://avatars.discourse-cdn.com/v4/letter/j/9dc877/32.png) [@jong99](https://discuss.elastic.co/u/jong99)\
**Post date:** [January 31, 2019, 12:22pm UTC](https://discuss.elastic.co/t/elasticsearch-requesttimeout-config-setting-being-ignored-by-visualisations/166549/1 "2019-01-31T12:22:08Z")

</div>

I'm using Kibana 6.6.0, installed through the official Docker image. The elasticsearch.requestTimeout seems to be being ignored by visualisations. Here is my kibana.yml config:

```
server.name: kibana
server.host: "0"
elasticsearch.url: http://elasticsearch:9200

server.ssl.key: my_cert.key
server.ssl.certificate: my_cert.crt
server.ssl.enabled: true

elasticsearch.requestTimeout: 60000

```

No matter what I set this value to though, visualisations seem to timeout at 30000 ms.

If I set a small value like `elasticsearch.requestTimeout: 12345` then I can see Timelion complaining about timeouts:  
 ![image](https://us1.discourse-cdn.com/elastic/original/3X/5/8/58323373ee30882172f5ceb76b435eb79805fccd.png)  
...so it's obviously picked up the config here.

However with this config all other standard visualisations (such as a simple metric visualisation) still seem to keep the default of 30000ms. When I inspect the POST requests going to the \_msearch endpoint I see this at the end:  
`...."filter":[{"match_all":{}}],"should":[],"must_not":[]}},"timeout":"30000ms"}`

which looks like this config setting is being ignored?

I'm confused! Any pointers on how to debug?

---

<div class="post-metadata">

**Author:** ![jong99](https://avatars.discourse-cdn.com/v4/letter/j/9dc877/32.png) [@jong99](https://discuss.elastic.co/u/jong99)\
**Post date:** [January 31, 2019, 12:30pm UTC](https://discuss.elastic.co/t/elasticsearch-requesttimeout-config-setting-being-ignored-by-visualisations/166549/2 "2019-01-31T12:30:21Z")

</div>

Finally found by reading the source the bit of code that does this, I should have been using:

```
elasticsearch.shardTimeout: 60000

```

Fixed!

---

<div class="post-metadata">

**Author:** ![tylersmalley](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tylersmalley/32/8833_2.png) [@tylersmalley](https://discuss.elastic.co/u/tylersmalley)\
**Post date:** [February 3, 2019, 3:48am UTC](https://discuss.elastic.co/t/elasticsearch-requesttimeout-config-setting-being-ignored-by-visualisations/166549/3 "2019-02-03T03:48:07Z")

</div>

Glad you figured it out - additionally I was going to make sure you didn't have `search.default_search_timeout` set in your cluster settings. You can view the current cluster settings from the ES API `localhost:9200/_cluster/settings?flat_settings=true`

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [March 3, 2019, 3:48am UTC](https://discuss.elastic.co/t/elasticsearch-requesttimeout-config-setting-being-ignored-by-visualisations/166549/4 "2019-03-03T03:48:21Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.