# Getting search request timeout after 60000ms **URL:** \ **Category:** Kibana\ **Created:** [November 26, 2019, 1:23pm UTC](https://discuss.elastic.co/t/getting-search-request-timeout-after-60000ms/209521 "2019-11-26T13:23:11Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Thedsk8](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thedsk8/32/46162_2.png) [@Thedsk8](https://discuss.elastic.co/u/Thedsk8)\ **Post date:** [November 26, 2019, 1:23pm UTC](https://discuss.elastic.co/t/getting-search-request-timeout-after-60000ms/209521/1 "2019-11-26T13:23:11Z")
We are currently using Elasticsearch 6.5 and getting intermittent request timeout for some dashboards. We are querying on approximately 550 GB data (76873087 documents) which is distributed among 3 indices. We have 6 data nodes of 64 GB each and 3 master nodes of 8 GB each. Each index has 6 shards and 1 replica. So should we increase the request timeout or decrease the amount of querying data or any other suggestion that you may have to resolve this? ---
**Author:** ![christophilus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christophilus/32/42991_2.png) [@christophilus](https://discuss.elastic.co/u/christophilus)\ **Post date:** [November 26, 2019, 5:04pm UTC](https://discuss.elastic.co/t/getting-search-request-timeout-after-60000ms/209521/2 "2019-11-26T17:04:31Z")
Those are your options, along with: beefing up your servers, optimizing your indices, scaling out, etc. If you can query for less data without negatively impacting your use cases, that's the ideal starting point, I'd say. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [December 24, 2019, 5:04pm UTC](https://discuss.elastic.co/t/getting-search-request-timeout-after-60000ms/209521/3 "2019-12-24T17:04:37Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.