# Trying to open a dashboard: Visualize: Request Timeout after 30000ms

**URL:** <https://discuss.elastic.co/t/trying-to-open-a-dashboard-visualize-request-timeout-after-30000ms/93749>\
**Category:** Kibana\
**Created:** [July 19, 2017, 11:28am UTC](https://discuss.elastic.co/t/trying-to-open-a-dashboard-visualize-request-timeout-after-30000ms/93749 "2017-07-19T11:28:05Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Olsen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/olsen/32/20228_2.png) [@Olsen](https://discuss.elastic.co/u/Olsen)\
**Post date:** [July 19, 2017, 11:28am UTC](https://discuss.elastic.co/t/trying-to-open-a-dashboard-visualize-request-timeout-after-30000ms/93749/1 "2017-07-19T11:28:05Z")

</div>

Hello..  
I 'am running Elasticsearch, Kibana and Logstach 5.2.2 in a Docker environment. Comming back from holiday I tried to open a saved dashboard that I know is working.

After 30 seconds of loading, Kibana respond with:

> Visualize: Request Timeout after 30000ms

I tried to reboot the linux box, but same result ☹

---

<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:** [July 19, 2017, 11:33am UTC](https://discuss.elastic.co/t/trying-to-open-a-dashboard-visualize-request-timeout-after-30000ms/93749/2 "2017-07-19T11:33:42Z")

</div>

That typically means Elasticsearch is slow responding. What is the specification of your Elasticsearch cluster? Which version are you running? How much data/indices/shards do you have in the cluster?

---

<div class="post-metadata">

**Author:** ![Olsen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/olsen/32/20228_2.png) [@Olsen](https://discuss.elastic.co/u/Olsen)\
**Post date:** [July 19, 2017, 12:16pm UTC](https://discuss.elastic.co/t/trying-to-open-a-dashboard-visualize-request-timeout-after-30000ms/93749/3 "2017-07-19T12:16:27Z")

</div>

Hi,,  
Kibana, Logstash and ES is running on the same Vmware image (CentOS7). Three different Docker containers.  
We have added three new FileBeat clients lately, so that can be the reason for slow response. A total of 10 clients.

I am a bit new to ES, Kibana and Logstash, but I'am learning fast 🙂 We are running 5.2.2 of the ES suite.

Here is some stats:

shards: 691  
heap.percent: 92  
ram.percent: 94  
cpu: 20  
heap total (MB): 71.24  
heap used(MB): 61.58  
indices: 140

Hope this helps..

---

<div class="post-metadata">

**Author:** ![Olsen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/olsen/32/20228_2.png) [@Olsen](https://discuss.elastic.co/u/Olsen)\
**Post date:** [August 14, 2017, 1:03pm UTC](https://discuss.elastic.co/t/trying-to-open-a-dashboard-visualize-request-timeout-after-30000ms/93749/4 "2017-08-14T13:03:17Z")

</div>

The server had only 8GB ram. I increased the memory to 16GB. That solved the problem. It was swapping too much.

---

<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:** [September 11, 2017, 1:04pm UTC](https://discuss.elastic.co/t/trying-to-open-a-dashboard-visualize-request-timeout-after-30000ms/93749/5 "2017-09-11T13:04:02Z")

</div>

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