# Error while querying elasticsearch **URL:** \ **Category:** Elasticsearch\ **Created:** [September 15, 2017, 5:20am UTC](https://discuss.elastic.co/t/error-while-querying-elasticsearch/100634 "2017-09-15T05:20:06Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![mruthyu](https://avatars.discourse-cdn.com/v4/letter/m/bb73d2/32.png) [@mruthyu](https://discuss.elastic.co/u/mruthyu)\ **Post date:** [September 15, 2017, 5:20am UTC](https://discuss.elastic.co/t/error-while-querying-elasticsearch/100634/1 "2017-09-15T05:20:07Z")
Ho to overcome the following issue? Whether increasing the search queue capacity or any other config parameter will help? Error: Request to Elasticsearch failed: {"error":{"root\_cause":[],"type":"search\_phase\_execution\_exception","reason":"","phase":"fetch","grouped":true,"failed\_shards":[],"caused\_by":{"type":"es\_rejected\_execution\_exception","reason":"rejected execution of org.elasticsearch.action.search.FetchSearchPhase$1@10a82f77 on EsThreadPoolExecutor[search, queue capacity = 1000, org.elasticsearch.common.util.concurrent.EsThreadPoolExecutor@5407c1e8[Running, pool size = 7, active threads = 7, queued tasks = 1000, completed tasks = 110165]]"}},"status":503} at [http://10.20.12.50:5601/bundles/kibana.bundle.js?v=15063:237:1333](http://10.20.12.50:5601/bundles/kibana.bundle.js?v=15063:237:1333) at Function.Promise.try ([http://10.20.12.50:5601/bundles/commons.bundle.js?v=15063:91:24383](http://10.20.12.50:5601/bundles/commons.bundle.js?v=15063:91:24383)) at [http://10.20.12.50:5601/bundles/commons.bundle.js?v=15063:91:23753](http://10.20.12.50:5601/bundles/commons.bundle.js?v=15063:91:23753) at Array.map () at Function.Promise.map ([http://10.20.12.50:5601/bundles/commons.bundle.js?v=15063:91:23708](http://10.20.12.50:5601/bundles/commons.bundle.js?v=15063:91:23708)) at callResponseHandlers ([http://10.20.12.50:5601/bundles/kibana.bundle.js?v=15063:237:949](http://10.20.12.50:5601/bundles/kibana.bundle.js?v=15063:237:949)) at [http://10.20.12.50:5601/bundles/kibana.bundle.js?v=15063:236:20482](http://10.20.12.50:5601/bundles/kibana.bundle.js?v=15063:236:20482) at processQueue ([http://10.20.12.50:5601/bundles/commons.bundle.js?v=15063:38:23621](http://10.20.12.50:5601/bundles/commons.bundle.js?v=15063:38:23621)) at [http://10.20.12.50:5601/bundles/commons.bundle.js?v=15063:38:23888](http://10.20.12.50:5601/bundles/commons.bundle.js?v=15063:38:23888) at Scope.$eval ([http://10.20.12.50:5601/bundles/commons.bundle.js?v=15063:39:4619](http://10.20.12.50:5601/bundles/commons.bundle.js?v=15063:39:4619)) at Scope.$digest ([http://10.20.12.50:5601/bundles/commons.bundle.js?v=15063:39:2359](http://10.20.12.50:5601/bundles/commons.bundle.js?v=15063:39:2359)) at Scope.$apply ([http://10.20.12.50:5601/bundles/commons.bundle.js?v=15063:39:5037](http://10.20.12.50:5601/bundles/commons.bundle.js?v=15063:39:5037)) at done ([http://10.20.12.50:5601/bundles/commons.bundle.js?v=15063:37:25027](http://10.20.12.50:5601/bundles/commons.bundle.js?v=15063:37:25027)) at completeRequest ([http://10.20.12.50:5601/bundles/commons.bundle.js?v=15063:37:28702](http://10.20.12.50:5601/bundles/commons.bundle.js?v=15063:37:28702)) at XMLHttpRequest.xhr.onload ([http://10.20.12.50:5601/bundles/commons.bundle.js?v=15063:37:29634](http://10.20.12.50:5601/bundles/commons.bundle.js?v=15063:37:29634)) ---
**Author:** ![poojagupta](https://avatars.discourse-cdn.com/v4/letter/p/5daacb/32.png) [@poojagupta](https://discuss.elastic.co/u/poojagupta)\ **Post date:** [September 15, 2017, 7:04am UTC](https://discuss.elastic.co/t/error-while-querying-elasticsearch/100634/2 "2017-09-15T07:04:16Z")
Hi, Which command you are using for serching into elasticsearch? also is you indices have data or only index is created ? please check ---
**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 15, 2017, 7:07am UTC](https://discuss.elastic.co/t/error-while-querying-elasticsearch/100634/3 "2017-09-15T07:07:46Z")
How many indices/shards are you targeting with each search? How many searches do you have running concurrently? ---
**Author:** ![mruthyu](https://avatars.discourse-cdn.com/v4/letter/m/bb73d2/32.png) [@mruthyu](https://discuss.elastic.co/u/mruthyu)\ **Post date:** [September 15, 2017, 8:47am UTC](https://discuss.elastic.co/t/error-while-querying-elasticsearch/100634/4 "2017-09-15T08:47:25Z")
Around 4456 shards as it is time based index. And I see this error from the dashboard where around 6-8 visualizations are 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:** [September 15, 2017, 8:48am UTC](https://discuss.elastic.co/t/error-while-querying-elasticsearch/100634/5 "2017-09-15T08:48:05Z")
How many data nodes in the cluster? What is your average shard size? ---
**Author:** ![mruthyu](https://avatars.discourse-cdn.com/v4/letter/m/bb73d2/32.png) [@mruthyu](https://discuss.elastic.co/u/mruthyu)\ **Post date:** [September 15, 2017, 8:49am UTC](https://discuss.elastic.co/t/error-while-querying-elasticsearch/100634/6 "2017-09-15T08:49:57Z")
Also this error has been seen while doing the search from discover page (Single request) and with time frame 10-15 minutes. ---
**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 15, 2017, 8:59am UTC](https://discuss.elastic.co/t/error-while-querying-elasticsearch/100634/7 "2017-09-15T08:59:45Z")
Unless you have a quite large number of data nodes, my guess is that you have too many small shards. When you refresh a dashboard, a task basically need to be created for every shard and every visualisation in the dashboard, and these are queued up to be processed. with 4456 shards being queried and 8 visualisations, you get over 35k tasks, which fills up all search queues quickly. The answer to this is not to increase the queue size, but rather to change how you index and shard your data. Try to make sure that your average shard size it at least a few GB in size, but ideally between 10GB and 30GB. ---
**Author:** ![mruthyu](https://avatars.discourse-cdn.com/v4/letter/m/bb73d2/32.png) [@mruthyu](https://discuss.elastic.co/u/mruthyu)\ **Post date:** [September 25, 2017, 7:25am UTC](https://discuss.elastic.co/t/error-while-querying-elasticsearch/100634/8 "2017-09-25T07:25:43Z")
Sure. Thanks. ---
**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 25, 2017, 7:26am UTC](https://discuss.elastic.co/t/error-while-querying-elasticsearch/100634/9 "2017-09-25T07:26:56Z")
This is quite a common issue, so I created [a blog post with some guidelines around shards and sharding](https://www.elastic.co/blog/how-many-shards-should-i-have-in-my-elasticsearch-cluster). ---
**Author:** ![mruthyu](https://avatars.discourse-cdn.com/v4/letter/m/bb73d2/32.png) [@mruthyu](https://discuss.elastic.co/u/mruthyu)\ **Post date:** [September 27, 2017, 5:58am UTC](https://discuss.elastic.co/t/error-while-querying-elasticsearch/100634/10 "2017-09-27T05:58:35Z")
Awesome blog. Thank you. ---
**Author:** ![mruthyu](https://avatars.discourse-cdn.com/v4/letter/m/bb73d2/32.png) [@mruthyu](https://discuss.elastic.co/u/mruthyu)\ **Post date:** [October 17, 2017, 1:44pm UTC](https://discuss.elastic.co/t/error-while-querying-elasticsearch/100634/11 "2017-10-17T13:44:05Z")
I have seen the following links and wanted to check if this issue is also related to the index templates/mappings. > [@Courier fetch: N of N shards failed](https://discuss.elastic.co/t/courier-fetch-n-of-n-shards-failed/27814/7): > > Does ismb.miki.vm.vcpu.usage exist in the logstash-2015.07.21 index? > > > recently I got the warning: > Courier Fetch: 17 of 100 shards failed. > > what cause …it and what can I do to fix it? > > thanks Akiva ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 14, 2017, 1:44pm UTC](https://discuss.elastic.co/t/error-while-querying-elasticsearch/100634/12 "2017-11-14T13:44:22Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.