# Courier Fetch: 70 of 80 shards failed

**URL:** <https://discuss.elastic.co/t/courier-fetch-70-of-80-shards-failed/80115>\
**Category:** Kibana\
**Created:** [March 27, 2017, 9:48am UTC](https://discuss.elastic.co/t/courier-fetch-70-of-80-shards-failed/80115 "2017-03-27T09:48:14Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![manopmk](https://avatars.discourse-cdn.com/v4/letter/m/b2d939/32.png) [@manopmk](https://discuss.elastic.co/u/manopmk)\
**Post date:** [March 27, 2017, 9:48am UTC](https://discuss.elastic.co/t/courier-fetch-70-of-80-shards-failed/80115/1 "2017-03-27T09:48:15Z")

</div>

i have added multiple log in logstash conf  
if i refresh kibana4 showing this  
**Courier Fetch: 70 of 80 shards failed.**  
for this i searched in google they told to add  
this line in elasticsearch.yml

threadpool.search.type: fixed  
threadpool.search.size: 200  
threadpool.search.queue\_size: 20000

but still its showing that error

note:im using mac  
using local ip

---

<div class="post-metadata">

**Author:** ![weltenwort](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/weltenwort/32/53885_2.png) [@weltenwort](https://discuss.elastic.co/u/weltenwort)\
**Post date:** [March 27, 2017, 10:38am UTC](https://discuss.elastic.co/t/courier-fetch-70-of-80-shards-failed/80115/2 "2017-03-27T10:38:50Z")

</div>

Hi @manopmk,

this sounds like Elasticsearch does not have enough resources to completely answer the query. Increasing the search threadpool size is a measure that might help, but like all performance parameters it is highly dependent on the runtime environment. The Elasticsearch log output might give some indication about the reason for the 10 failed shards.

---

<div class="post-metadata">

**Author:** ![manopmk](https://avatars.discourse-cdn.com/v4/letter/m/b2d939/32.png) [@manopmk](https://discuss.elastic.co/u/manopmk)\
**Post date:** [March 27, 2017, 10:48am UTC](https://discuss.elastic.co/t/courier-fetch-70-of-80-shards-failed/80115/3 "2017-03-27T10:48:27Z")

</div>

Thank you buddy  
in **es log**  
org.elasticsearch.search.SearchParseException: [logstash-2016.10.21][4]: from[-1],size[500]: Parse Failure [Failed to parse source [{"size":500,"sort":{"tstamp":"asc"},"query":{"filtered":{"query":{"query\_string":{"analyze\_wildcard":true,"query":"_"}},"filter":{"bool":{"must":[{"range":{"tstamp":{"gte":1490595144374,"lte":1490609544374}}}],"must\_not":[]}}}},"highlight":{"pre\_tags":["@kibana-highlighted-field@"],"post\_tags":["@/kibana-highlighted-field@"],"fields":{"_":{}}},"aggs":{"2":{"date\_histogram":{"field":"tstamp","interval":"5m","pre\_zone":"+05:30","pre\_zone\_adjust\_large\_interval":true,"min\_doc\_count":0,"extended\_bounds":{"min":1490595144374,"max":1490609544374}}}},"fields":["\*","\_source"],"script\_fields":{},"fielddata\_fields":["\_timestamp","@timestamp","tstamp"]}]]  
Parse Failure [No mapping found for [tstamp] in order to sort on]];

Actullay i created index called **tstamp which contain exact time stamp of log**  
**my conf**

filter {  
grok {  
match =\> ["message", "%{DATESTAMP:timestamp}"]  
}  
date {  
locale =\> "en"  
match =\> ["timestamp", "MM-dd-YYYY HH:mm:ss","ISO8601"]  
target =\> ["tstamp"]  
remove\_field =\> ["timestamp"]   
}  
}  
**Json i got**  
"message" =\> "03-27-2017 10:26:11 INFO - in DAO Impl query: fetching username from username\_notification table",  
"@version" =\> "1",  
"@timestamp" =\> "2017-03-27T09:33:50.768Z",  
"host" =\> "Vishnu-Prasad.local",  
"path" =\> "/Users/tcstsb3/Downloads/batch/starbuck-batch-service.log",  
"tstamp" =\> "2017-03-27T04:56:11.000Z"  
}

in kibana i added new index called tstamp i overrided the changes  
but i dont know why this showing **No mapping found**

can you plz help me

---

<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:** [April 24, 2017, 10:48am UTC](https://discuss.elastic.co/t/courier-fetch-70-of-80-shards-failed/80115/4 "2017-04-24T10:48:45Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.