# Dashboard Timeout - Data might be incomplete because your request timed out

**URL:** <https://discuss.elastic.co/t/dashboard-timeout-data-might-be-incomplete-because-your-request-timed-out/212808>\
**Category:** Kibana\
**Tags:** docker\
**Created:** [December 23, 2019, 6:07am UTC](https://discuss.elastic.co/t/dashboard-timeout-data-might-be-incomplete-because-your-request-timed-out/212808 "2019-12-23T06:07:40Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![BALA\_BALA](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bala_bala/32/44655_2.png) [@BALA\_BALA](https://discuss.elastic.co/u/BALA_BALA)\
**Post date:** [December 23, 2019, 6:07am UTC](https://discuss.elastic.co/t/dashboard-timeout-data-might-be-incomplete-because-your-request-timed-out/212808/1 "2019-12-23T06:07:40Z")

</div>

Hi Team,

I am getting timeout error "Data might be incomplete because your request timed out" while retrieving 12.5GB of data in Kibana dashboard.  
timeout increased from 30000 to "elasticsearch.requestTimeout: 90000" .  
Please suggest if i need to tune any other parameters .

System Memory Details.

MemTotal: 32892852 kB  
MemFree: 4041332 kB  
MemAvailable: 11423120 kB  
Buffers: 275688 kB  
Cached: 7365620 kB  
SwapCached: 41288 kB  
Active: 5699920 kB  
Inactive: 4164440 kB  
Active(anon): 2142368 kB  
Inactive(anon): 750992 kB  
Active(file): 3557552 kB  
Inactive(file): 3413448 kB  
Unevictable: 17697984 kB  
Mlocked: 17697984 kB  
SwapTotal: 4194300 kB  
SwapFree: 3381500 kB

---

<div class="post-metadata">

**Author:** ![bhavyarm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bhavyarm/32/22392_2.png) [@bhavyarm](https://discuss.elastic.co/u/bhavyarm)\
**Post date:** [December 24, 2019, 1:25am UTC](https://discuss.elastic.co/t/dashboard-timeout-data-might-be-incomplete-because-your-request-timed-out/212808/2 "2019-12-24T01:25:52Z")

</div>

@jbudz I think the data size here too much for Kibana to handle?

Thanks  
Bhavya

---

<div class="post-metadata">

**Author:** ![BALA\_BALA](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bala_bala/32/44655_2.png) [@BALA\_BALA](https://discuss.elastic.co/u/BALA_BALA)\
**Post date:** [December 24, 2019, 2:09am UTC](https://discuss.elastic.co/t/dashboard-timeout-data-might-be-incomplete-because-your-request-timed-out/212808/3 "2019-12-24T02:09:16Z")

</div>

Hi Bhavya, I don't think so, i belive some parameter have to tune...i tried increasing memory and also enabled below two options but still getting the same error.  
elasticsearch.requestTimeout: 90000  
elasticsearch.shardTimeout: 60000

---

<div class="post-metadata">

**Author:** ![jbudz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jbudz/32/45922_2.png) [@jbudz](https://discuss.elastic.co/u/jbudz)\
**Post date:** [December 24, 2019, 3:18pm UTC](https://discuss.elastic.co/t/dashboard-timeout-data-might-be-incomplete-because-your-request-timed-out/212808/4 "2019-12-24T15:18:56Z")

</div>

Hey - those are the correct options for increasing the wait time. They'll work up to a maximum of two minutes. Beyond that we usually start looking into why the queries are taking so long and what we can optimize. Some of the parameters you're thinking of include:

- number of visualizations in the dashboard
- chart intervals (the more data points, the more load)
- cluster load. how's the hardware on the cluster looking?
- shard settings for the indices you're querying? too many shards and we'll see slow queries

I'd +1 @bhavyarm - 12.5gb is a lot to handle. It's going to cause significant strain on the browser that has to load all of this in memory, so less data would be ideal in addition any optimizations we can do.

---

<div class="post-metadata">

**Author:** ![BALA\_BALA](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bala_bala/32/44655_2.png) [@BALA\_BALA](https://discuss.elastic.co/u/BALA_BALA)\
**Post date:** [January 8, 2020, 2:49am UTC](https://discuss.elastic.co/t/dashboard-timeout-data-might-be-incomplete-because-your-request-timed-out/212808/5 "2020-01-08T02:49:12Z")

</div>

Thanks Jon. I just added below parameter and also increased the RAM. So far no timeout occurred.

1. elasticsearch.shardTimeout: 30000  
2 . Xms24g -Xmx24g" [Recommendation is 30G-will increase more in the future.]

---

<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:** [February 5, 2020, 2:49am UTC](https://discuss.elastic.co/t/dashboard-timeout-data-might-be-incomplete-because-your-request-timed-out/212808/6 "2020-02-05T02:49:16Z")

</div>

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