# KIBANA TIMEOUT Request Timeout after 30000ms **URL:** \ **Category:** Kibana\ **Created:** [June 12, 2017, 7:39pm UTC](https://discuss.elastic.co/t/kibana-timeout-request-timeout-after-30000ms/89097 "2017-06-12T19:39:02Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Vivek\_Raj](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vivek_raj/32/45342_2.png) [@Vivek\_Raj](https://discuss.elastic.co/u/Vivek_Raj)\ **Post date:** [June 12, 2017, 7:39pm UTC](https://discuss.elastic.co/t/kibana-timeout-request-timeout-after-30000ms/89097/1 "2017-06-12T19:39:02Z")
Hi Team, We are using Kibana version: 4.5.0, when we try to query requiring analysis of large volume of historical data (like 6 months). Its throwing Error: Request Timeout after 30000ms. We have 7 Elastic search servers cluster and we have kafka cluster in between logstash and Elasticsearch. Elasticsearch version: 2.5 If we change Timeout 30000ms on kibana.yml to timeout= 90000ms will it work? Please have a look, Appreciate quick response. Thanks Vivek. ---
**Author:** ![Stacey\_Gammon](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stacey_gammon/32/14025_2.png) [@Stacey\_Gammon](https://discuss.elastic.co/u/Stacey_Gammon)\ **Post date:** [June 12, 2017, 7:54pm UTC](https://discuss.elastic.co/t/kibana-timeout-request-timeout-after-30000ms/89097/2 "2017-06-12T19:54:19Z")
Looks like `requestTimeout` is the appropriate setting to try according to [https://www.elastic.co/guide/en/kibana/4.5/kibana-server-properties.html](https://www.elastic.co/guide/en/kibana/4.5/kibana-server-properties.html). Please give it a try and see if it helps. ---
**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:** [June 12, 2017, 8:09pm UTC](https://discuss.elastic.co/t/kibana-timeout-request-timeout-after-30000ms/89097/3 "2017-06-12T20:09:13Z")
This is more of an Elasticsearch query, as it is Elasticsearch that is doing all the work behind the scenes. What is the specification of the nodes in the cluster? How much data do you have per node? How much of this are you querying when you see these very large latencies? How many indices and shards do you have in the cluster? ---
**Author:** ![Vivek\_Raj](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vivek_raj/32/45342_2.png) [@Vivek\_Raj](https://discuss.elastic.co/u/Vivek_Raj)\ **Post date:** [June 13, 2017, 3:31pm UTC](https://discuss.elastic.co/t/kibana-timeout-request-timeout-after-30000ms/89097/4 "2017-06-13T15:31:26Z")
Node Specifications: 4 VCPUs, 320GB DISK, 16 GB RAM index.number\_of\_shards: 1 Indices 652 DATA we get per day to single ES node is 2.6 gb. @Christian_Dahlqvist ---
**Author:** ![Vivek\_Raj](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vivek_raj/32/45342_2.png) [@Vivek\_Raj](https://discuss.elastic.co/u/Vivek_Raj)\ **Post date:** [June 13, 2017, 3:32pm UTC](https://discuss.elastic.co/t/kibana-timeout-request-timeout-after-30000ms/89097/5 "2017-06-13T15:32:17Z")
@Stacey_Gammon Thank You will try to increase requestTimeout ---
**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:** [June 13, 2017, 3:38pm UTC](https://discuss.elastic.co/t/kibana-timeout-request-timeout-after-30000ms/89097/6 "2017-06-13T15:38:48Z")
How many indices do you create every day? How many of these are you querying when you see the high latency? What type of storage do you have? Have you tried to identify what is limiting performance when you are querying, e.g. CPU utilisation or iowait? ---
**Author:** ![Vivek\_Raj](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vivek_raj/32/45342_2.png) [@Vivek\_Raj](https://discuss.elastic.co/u/Vivek_Raj)\ **Post date:** [June 13, 2017, 8:08pm UTC](https://discuss.elastic.co/t/kibana-timeout-request-timeout-after-30000ms/89097/7 "2017-06-13T20:08:40Z")
4 indices are created everyday. All 4 indices gets queried when we try to view the dashboard as we are adding visualization from all these 3 indices. We have open stack cloud environment. ---
**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:** [June 13, 2017, 9:03pm UTC](https://discuss.elastic.co/t/kibana-timeout-request-timeout-after-30000ms/89097/8 "2017-06-13T21:03:21Z")
That is a lot of quite small indices to query, which can be inefficient. I suspect you would be better off using weekly or monthly indices given the volumes you mentioned. As you did not answer my other questions, it it difficult to know exactly what the bottleneck is. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 11, 2017, 9:04pm UTC](https://discuss.elastic.co/t/kibana-timeout-request-timeout-after-30000ms/89097/9 "2017-07-11T21:04:02Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.