# Kibana Dashboard Timeout

**URL:** <https://discuss.elastic.co/t/kibana-dashboard-timeout/128201>\
**Category:** Kibana\
**Created:** [April 16, 2018, 1:53pm UTC](https://discuss.elastic.co/t/kibana-dashboard-timeout/128201 "2018-04-16T13:53:10Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![kmroz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kmroz/32/62741_2.png) [@kmroz](https://discuss.elastic.co/u/kmroz)\
**Post date:** [April 16, 2018, 1:53pm UTC](https://discuss.elastic.co/t/kibana-dashboard-timeout/128201/1 "2018-04-16T13:53:10Z")

</div>

Hello it seems we keep running into a timeout after trying to look back at a days work of data. It works fine 12 hours or less. Once i try to query 24hrs or more , i get a time out in Kibana. I am using Kibana 6.1.1 . the data set we are looking at is roughly 100gb.

---

<div class="post-metadata">

**Author:** ![Bill\_McConaghy](https://avatars.discourse-cdn.com/v4/letter/b/ed655f/32.png) [@Bill\_McConaghy](https://discuss.elastic.co/u/Bill_McConaghy)\
**Post date:** [April 16, 2018, 2:06pm UTC](https://discuss.elastic.co/t/kibana-dashboard-timeout/128201/2 "2018-04-16T14:06:27Z")

</div>

You could consider upping the default value of elasticsearch.requestTimeout from 30000 milliseconds in your kibana.yml. This might allow you use a larger window. Are you using scripted fields? This might be the cause of things taking so long.

---

<div class="post-metadata">

**Author:** ![kmroz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kmroz/32/62741_2.png) [@kmroz](https://discuss.elastic.co/u/kmroz)\
**Post date:** [April 16, 2018, 2:22pm UTC](https://discuss.elastic.co/t/kibana-dashboard-timeout/128201/3 "2018-04-16T14:22:18Z")

</div>

is there a recommendation to change the value to, as I dont want to over do it since this then can not time out when there is an actual issue? I am not using scripted fields..

---

<div class="post-metadata">

**Author:** ![Bill\_McConaghy](https://avatars.discourse-cdn.com/v4/letter/b/ed655f/32.png) [@Bill\_McConaghy](https://discuss.elastic.co/u/Bill_McConaghy)\
**Post date:** [April 16, 2018, 2:32pm UTC](https://discuss.elastic.co/t/kibana-dashboard-timeout/128201/4 "2018-04-16T14:32:59Z")

</div>

I would maybe try doubling it to 60000 and see if it helps. I would not recommend going above 2 minutes (120000).

---

<div class="post-metadata">

**Author:** ![kmroz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kmroz/32/62741_2.png) [@kmroz](https://discuss.elastic.co/u/kmroz)\
**Post date:** [April 16, 2018, 3:18pm UTC](https://discuss.elastic.co/t/kibana-dashboard-timeout/128201/5 "2018-04-16T15:18:58Z")

</div>

ok will give that a go. Thanks!

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [April 16, 2018, 3:49pm UTC](https://discuss.elastic.co/t/kibana-dashboard-timeout/128201/6 "2018-04-16T15:49:51Z")

</div>

What is the size of your cluster? What hardware are you using? How many visualisations do you have on the dashboard that is timing out? What type of visualisation?

---

<div class="post-metadata">

**Author:** ![kmroz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kmroz/32/62741_2.png) [@kmroz](https://discuss.elastic.co/u/kmroz)\
**Post date:** [April 16, 2018, 4:20pm UTC](https://discuss.elastic.co/t/kibana-dashboard-timeout/128201/7 "2018-04-16T16:20:50Z")

</div>

we have 12 ES nodes 4 LS nodes and 1 kibana Node. ES has 40 cores, 250 gb ram

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [April 16, 2018, 4:38pm UTC](https://discuss.elastic.co/t/kibana-dashboard-timeout/128201/8 "2018-04-16T16:38:34Z")

</div>

How many visualisations do you have on the dashboard that is timing out? What type of visualisation?

---

<div class="post-metadata">

**Author:** ![kmroz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kmroz/32/62741_2.png) [@kmroz](https://discuss.elastic.co/u/kmroz)\
**Post date:** [April 16, 2018, 4:46pm UTC](https://discuss.elastic.co/t/kibana-dashboard-timeout/128201/9 "2018-04-16T16:46:48Z")

</div>

two visualizations, one is a Timelion one and the other is a table.

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [April 16, 2018, 4:53pm UTC](https://discuss.elastic.co/t/kibana-dashboard-timeout/128201/10 "2018-04-16T16:53:02Z")

</div>

Sounds odd. What is the load on the cluster? What does CPU usage, disk I/O and iowait look like?

---

<div class="post-metadata">

**Author:** ![kmroz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kmroz/32/62741_2.png) [@kmroz](https://discuss.elastic.co/u/kmroz)\
**Post date:** [April 16, 2018, 4:56pm UTC](https://discuss.elastic.co/t/kibana-dashboard-timeout/128201/11 "2018-04-16T16:56:43Z")

</div>

its all low, 2% CPU load is ~1.03

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [April 16, 2018, 4:58pm UTC](https://discuss.elastic.co/t/kibana-dashboard-timeout/128201/12 "2018-04-16T16:58:05Z")

</div>

Anything in the Elasticsearch logs, e.g. long or frequent GC?

---

<div class="post-metadata">

**Author:** ![kmroz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kmroz/32/62741_2.png) [@kmroz](https://discuss.elastic.co/u/kmroz)\
**Post date:** [April 16, 2018, 5:01pm UTC](https://discuss.elastic.co/t/kibana-dashboard-timeout/128201/13 "2018-04-16T17:01:21Z")

</div>

i havent touched GC that already comes with ES. So i would assume that is not an issue? Logs are clear of anything else.

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [April 16, 2018, 5:02pm UTC](https://discuss.elastic.co/t/kibana-dashboard-timeout/128201/14 "2018-04-16T17:02:36Z")

</div>

Are there any log messages about GC in the logs?

---

<div class="post-metadata">

**Author:** ![kmroz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kmroz/32/62741_2.png) [@kmroz](https://discuss.elastic.co/u/kmroz)\
**Post date:** [April 16, 2018, 5:09pm UTC](https://discuss.elastic.co/t/kibana-dashboard-timeout/128201/15 "2018-04-16T17:09:31Z")

</div>

There is nothing about GC

---

<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:** [May 14, 2018, 5:09pm UTC](https://discuss.elastic.co/t/kibana-dashboard-timeout/128201/16 "2018-05-14T17:09:38Z")

</div>

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