# Discover: Request Timeout after 30000ms: ES
**URL:** https://discuss.elastic.co/t/discover-request-timeout-after-30000ms-es/131400
**Category:** Elasticsearch
**Created:** [May 11, 2018, 5:58am UTC](https://discuss.elastic.co/t/discover-request-timeout-after-30000ms-es/131400 "2018-05-11T05:58:39Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@rahulnama](https://discuss.elastic.co/u/rahulnama)
#### Post date: [May 11, 2018, 5:58am UTC](https://discuss.elastic.co/t/discover-request-timeout-after-30000ms-es/131400/1 "2018-05-11T05:58:39Z")
Hello Team
Greetings of the day!
I'm using ES on a node.
Node Specifications:
2 VCPUs, 50GB DISK, 8 GB RAM
Indices 4
Every Indice has less than 100mb of data.
When I'm trying to visualise an indice data in discover, it's displaying Request Timeout error as CPU is being utilized 100%. I have 10 shards for that particular indice.
Is there anything that I could to here to avoid this? I read I can increase the timeout but doing so will help me? is it a best practice?
Please do suggest. Thanks for your time as always
Rahul Nama
---
### Author:  [@thiago](https://discuss.elastic.co/u/thiago)
#### Post date: [May 19, 2018, 4:39am UTC](https://discuss.elastic.co/t/discover-request-timeout-after-30000ms-es/131400/2 "2018-05-19T04:39:15Z")
How much heap is set to JVM? Also, how many shards are there is this node (considering all open indices)?
---
### Author:  [@rahulnama](https://discuss.elastic.co/u/rahulnama)
#### Post date: [May 23, 2018, 5:02am UTC](https://discuss.elastic.co/t/discover-request-timeout-after-30000ms-es/131400/3 "2018-05-23T05:02:05Z")
Hello @thiago
I have 12 shards in this node. and heap memory set to jvm is 4GB.
---
### Author:  [@thiago](https://discuss.elastic.co/u/thiago)
#### Post date: [May 23, 2018, 6:57pm UTC](https://discuss.elastic.co/t/discover-request-timeout-after-30000ms-es/131400/4 "2018-05-23T18:57:16Z")
So 2 VCPUs is not enough for that. We recommend at least for 4 cores. You can check [Nodes hot\_threads](https://www.elastic.co/guide/en/elasticsearch/reference/current/cluster-nodes-hot-threads.html) to get a better understanding of what's burning CPU.
---
### Author:  [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [May 23, 2018, 7:04pm UTC](https://discuss.elastic.co/t/discover-request-timeout-after-30000ms-es/131400/5 "2018-05-23T19:04:33Z")
What is the average size of your documents? You can try disabling highlighting by setting `doc_table:highlight` to `false` under the [advanced options tab](https://www.elastic.co/guide/en/kibana/6.2/advanced-options.html) as this can reduce CPU usage quite a bit.
---
### Author:  [@rahulnama](https://discuss.elastic.co/u/rahulnama)
#### Post date: [May 24, 2018, 10:41am UTC](https://discuss.elastic.co/t/discover-request-timeout-after-30000ms-es/131400/6 "2018-05-24T10:41:31Z")
@Christian_Dahlqvist
Size of Documents is very less(in kbs). Sure I will do that and give one more try
Thank you 🙂
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [June 21, 2018, 10:41am UTC](https://discuss.elastic.co/t/discover-request-timeout-after-30000ms-es/131400/7 "2018-06-21T10:41:38Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.