# Request Timeout after 30000ms | kibana 4 error **URL:** \ **Category:** Elasticsearch\ **Created:** [August 31, 2018, 3:52pm UTC](https://discuss.elastic.co/t/request-timeout-after-30000ms-kibana-4-error/146892 "2018-08-31T15:52:26Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![rajkumar.m](https://avatars.discourse-cdn.com/v4/letter/r/e9bcb4/32.png) [@rajkumar.m](https://discuss.elastic.co/u/rajkumar.m)\ **Post date:** [August 31, 2018, 3:52pm UTC](https://discuss.elastic.co/t/request-timeout-after-30000ms-kibana-4-error/146892/1 "2018-08-31T15:52:26Z")
when i click on indices tab on Kibana settings Menu, i am getting "Request Timeout after 30000ms " error. someone please help and advise how can i increase the value. I am using elastic/kibana version 4. ![image](https://us1.discourse-cdn.com/elastic/original/3X/c/6/c629d15695974fad80d8b5bec8844582116429bc.jpeg) ![image](https://us1.discourse-cdn.com/elastic/original/3X/a/5/a5d2c51b783c76654d45bd8a744c57d3828aa449.png) ---
**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:** [August 31, 2018, 4:05pm UTC](https://discuss.elastic.co/t/request-timeout-after-30000ms-kibana-4-error/146892/2 "2018-08-31T16:05:21Z")
I have not used that version in years, but it looks like `elasticsearch.requestTimeout` can be specified [in the Kibana config file](https://www.elastic.co/guide/en/kibana/4.6/kibana-server-properties.html). ---
**Author:** ![rajkumar.m](https://avatars.discourse-cdn.com/v4/letter/r/e9bcb4/32.png) [@rajkumar.m](https://discuss.elastic.co/u/rajkumar.m)\ **Post date:** [August 31, 2018, 5:29pm UTC](https://discuss.elastic.co/t/request-timeout-after-30000ms-kibana-4-error/146892/3 "2018-08-31T17:29:28Z")
Thanks Christian for your response !! is this setting applicable for both Kibana 4 & 5 ? ---
**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:** [August 31, 2018, 5:37pm UTC](https://discuss.elastic.co/t/request-timeout-after-30000ms-kibana-4-error/146892/4 "2018-08-31T17:37:40Z")
Probably, but I would always recommend checking the documentation for your particular version. It may also be worthwhile looking into why it times out in the first place. Do you have too much data for your cluster? Do you have too many small shards? Have you outgrown your hardware? ---
**Author:** ![rajkumar.m](https://avatars.discourse-cdn.com/v4/letter/r/e9bcb4/32.png) [@rajkumar.m](https://discuss.elastic.co/u/rajkumar.m)\ **Post date:** [August 31, 2018, 5:50pm UTC](https://discuss.elastic.co/t/request-timeout-after-30000ms-kibana-4-error/146892/5 "2018-08-31T17:50:09Z")
We were unable to determine, please let me know how to find out, we are seeing this issue recently. we are tying to understand the recommended shard size. infact we are pushing the structured data directly to elastic search with curl. we are not using filebeat/logstash at present. ---
**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:** [August 31, 2018, 5:52pm UTC](https://discuss.elastic.co/t/request-timeout-after-30000ms-kibana-4-error/146892/6 "2018-08-31T17:52:26Z")
Can you provide the output of the [cluster stats API](https://www.elastic.co/guide/en/elasticsearch/reference/2.4/cluster-stats.html) and describe the use case? ---
**Author:** ![rajkumar.m](https://avatars.discourse-cdn.com/v4/letter/r/e9bcb4/32.png) [@rajkumar.m](https://discuss.elastic.co/u/rajkumar.m)\ **Post date:** [August 31, 2018, 6:01pm UTC](https://discuss.elastic.co/t/request-timeout-after-30000ms-kibana-4-error/146892/7 "2018-08-31T18:01:25Z")
Use case is we are capturing predefined health check values/outputs from our clients with our health check scripts running in specific intervals and pushing it to elastic search in structured data with json, once data is available on elastic and kibana generating dashboards. { "timestamp" : 1535738104784, "cluster\_name" : "XXXXXXX\_CLUSTER", "status" : "green", "indices" : { "count" : 117, "shards" : { "total" : 234, "primaries" : 117, "replication" : 1.0, "index" : { "shards" : { "min" : 2, "max" : 2, "avg" : 2.0 }, "primaries" : { "min" : 1, "max" : 1, "avg" : 1.0 }, "replication" : { "min" : 1.0, "max" : 1.0, "avg" : 1.0 } } }, "docs" : { "count" : 123255603, "deleted" : 61785 }, "store" : { "size" : "54gb", "size\_in\_bytes" : 57987858300, "throttle\_time" : "0s", "throttle\_time\_in\_millis" : 0 }, "fielddata" : { "memory\_size" : "3.2mb", "memory\_size\_in\_bytes" : 3396488, "evictions" : 0 }, "query\_cache" : { "memory\_size" : "277.2mb", "memory\_size\_in\_bytes" : 290747824, "total\_count" : 27927453, "hit\_count" : 1681824, "miss\_count" : 26245629, "cache\_size" : 7000, "cache\_count" : 21452, "evictions" : 14452 }, "completion" : { "size" : "0b", "size\_in\_bytes" : 0 }, "segments" : { "count" : 2193, "memory" : "166.4mb", "memory\_in\_bytes" : 174572590, "terms\_memory" : "126.5mb", "terms\_memory\_in\_bytes" : 132707094, "stored\_fields\_memory" : "31.7mb", "stored\_fields\_memory\_in\_bytes" : 33287064, "term\_vectors\_memory" : "0b", "term\_vectors\_memory\_in\_bytes" : 0, "norms\_memory" : "1.6mb", "norms\_memory\_in\_bytes" : 1716864, "doc\_values\_memory" : "6.5mb", "doc\_values\_memory\_in\_bytes" : 6861568, "index\_writer\_memory" : "565.9kb", "index\_writer\_memory\_in\_bytes" : 579565, "index\_writer\_max\_memory" : "19gb", "index\_writer\_max\_memory\_in\_bytes" : 20501446656, "version\_map\_memory" : "4.7kb", "version\_map\_memory\_in\_bytes" : 4908, "fixed\_bit\_set" : "0b", "fixed\_bit\_set\_memory\_in\_bytes" : 0 }, "percolate" : { "total" : 0, "time" : "0s", "time\_in\_millis" : 0, "current" : 0, "memory\_size\_in\_bytes" : -1, "memory\_size" : "-1b", "queries" : 0 } }, "nodes" : { "count" : { "total" : 7, "master\_only" : 3, "data\_only" : 2, "master\_data" : 0, "client" : 0 }, "versions" : ["2.4.2"], "os" : { "available\_processors" : 42, "allocated\_processors" : 42, "mem" : { "total" : "88.5gb", "total\_in\_bytes" : 95035625472 }, "names" : [ { "name" : "Linux", "count" : 7 } ] }, "process" : { "cpu" : { "percent" : 9 }, "open\_file\_descriptors" : { "min" : 276, "max" : 2479, "avg" : 888 } }, "jvm" : { "max\_uptime" : "1.6d", "max\_uptime\_in\_millis" : 145886310, "versions" : [ { "version" : "1.8.0\_121", "vm\_name" : "Java HotSpot(TM) 64-Bit Server VM", "vm\_version" : "25.121-b13", "vm\_vendor" : "Oracle Corporation", "count" : 7 } ], "mem" : { "heap\_used" : "65.6gb", "heap\_used\_in\_bytes" : 70541977232, "heap\_max" : "182gb", "heap\_max\_in\_bytes" : 195467804672 }, "threads" : 575 }, "fs" : { "total" : "1.3tb", "total\_in\_bytes" : 1527597965312, "free" : "1.3tb", "free\_in\_bytes" : 1468908515328, "available" : "1.2tb", "available\_in\_bytes" : 1391276986368, "spins" : "true" }, "plugins" : [ { "name" : "license", "version" : "2.4.2", "description" : "Internal Elasticsearch Licensing Plugin", "jvm" : true, "classname" : "org.elasticsearch.license.plugin.LicensePlugin", "isolated" : false, "site" : false }, { "name" : "shield", "version" : "2.4.2", "description" : "Elasticsearch Shield (security)", "jvm" : true, "classname" : "org.elasticsearch.shield.ShieldPlugin", "isolated" : false, "site" : false } ] } } ---
**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:** [August 31, 2018, 6:06pm UTC](https://discuss.elastic.co/t/request-timeout-after-30000ms-kibana-4-error/146892/8 "2018-08-31T18:06:21Z")
That looks fine as far as I can tell. You have a quite large number of shards given the data volume, which could have an impact, but it is not extreme. Have you tried to identify what is limiting performance, e.g. CPU usage, disk I/O etc? ---
**Author:** ![rajkumar.m](https://avatars.discourse-cdn.com/v4/letter/r/e9bcb4/32.png) [@rajkumar.m](https://discuss.elastic.co/u/rajkumar.m)\ **Post date:** [August 31, 2018, 10:24pm UTC](https://discuss.elastic.co/t/request-timeout-after-30000ms-kibana-4-error/146892/9 "2018-08-31T22:24:17Z")
i don't find issue with respect to CPU,Memory utilization, only one of the master node is using 70%. how to find why my master nodes are not same CPU usage. ---
**Author:** ![rajkumar.m](https://avatars.discourse-cdn.com/v4/letter/r/e9bcb4/32.png) [@rajkumar.m](https://discuss.elastic.co/u/rajkumar.m)\ **Post date:** [September 6, 2018, 5:14pm UTC](https://discuss.elastic.co/t/request-timeout-after-30000ms-kibana-4-error/146892/10 "2018-09-06T17:14:28Z")
Hi, Please advise how can we config number shards, is this based on indexes or CPU/Memory/Disk ? please refer the above configuration which i have pasted. ---
**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:** [September 6, 2018, 5:54pm UTC](https://discuss.elastic.co/t/request-timeout-after-30000ms-kibana-4-error/146892/11 "2018-09-06T17:54:47Z")
Elasticsearch can be quite I/O intensive, so also check I/O statistics, e.g. using `iostat`. How much RAM do the hosts with your data nodes have? How much have you assigned to heap out of this? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [October 4, 2018, 5:54pm UTC](https://discuss.elastic.co/t/request-timeout-after-30000ms-kibana-4-error/146892/12 "2018-10-04T17:54:51Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.