# Failed shards in search response, but no reasons

**URL:** <https://discuss.elastic.co/t/failed-shards-in-search-response-but-no-reasons/8774>\
**Category:** Elasticsearch\
**Created:** [August 17, 2012, 6:50pm UTC](https://discuss.elastic.co/t/failed-shards-in-search-response-but-no-reasons/8774 "2012-08-17T18:50:06Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Josh\_Holtzman](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/josh_holtzman/32/1890_2.png) [@Josh\_Holtzman](https://discuss.elastic.co/u/Josh_Holtzman)\
**Post date:** [August 17, 2012, 6:50pm UTC](https://discuss.elastic.co/t/failed-shards-in-search-response-but-no-reasons/8774/1 "2012-08-17T18:50:06Z")

</div>

When running load tests with many concurrent threads, I'll occasionally see  
a result like this:

{"took":1,"timed\_out":false,"\_shards":{"total":2,"successful":1,"failed":1},"hits":{"total":0,"max\_score":null,"hits":[]}}

Notice the missing "failures" array. I also see nothing in the logs. Does  
anyone have any idea why this would occur, and why it happens more  
frequently when there are more concurrent searches?

I'm running v0.19.2

Thanks,  
Josh

--

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 3:16am UTC](https://discuss.elastic.co/t/failed-shards-in-search-response-but-no-reasons/8774/2 "2017-07-06T03:16:01Z")

</div>