When I try to load a dashboard in Kibana on my Amazon Elasticsearch Service domain, it returns the "Courier fetch: n of m shards failed" error. Example:

Error: Courier Fetch: 5 of 60 shards failed

Note: There are many possible causes of this error. Four common resolutions are discussed here.

The cluster node that receives the search request from the client coordinates the execution of the query across all relevant nodes. The courier fetch error occurs when the request that is sent by the coordinating node times out before it receives a response from all relevant shards. For more information, see Query Phase and Fetch Phase in the Elasticsearch documentation.

Use one or more of the following methods to resolve the courier fetch error:

Consider resizing your cluster

Confirm that you are following the instance sizing best practices that are appropriate for your use case. For more information, see Choosing Instance Types and Testing.

Reduce the scope of your query

For example, if you query on time frame, reduce the date range or filter the results by configuring the index pattern in Kibana.

Avoid executing select * queries on large indices

Instead, use filters to query a part of the index and search as few fields as possible.

Reindex and reduce the number of shards

The more shards you have in your Elasticsearch cluster, the more likely you are to get the courier fetch error. Because each shard has its own resource allocation and overheads, a large number of shards places excessive strain on the cluster. To reduce the number of shards in your cluster, see My Amazon Elasticsearch Service domain has been stuck in the Processing state for a long time.


Did this page help you? Yes | No

Back to the AWS Support Knowledge Center

Need help? Visit the AWS Support Center.

Published: 2018-11-14