Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many errors.
To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them. Take a self-guided product tour to see for yourself (no registration required).
This guide will help you check for common problems that cause the log ” Failed to execute pipeline ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: filter.
Overview
A filter in Elasticsearch is all about applying some conditions inside the query that are used to narrow down the matching result set.
What it is used for
When a query is executed, Elasticsearch by default calculates the relevance score of the matching documents. But in some conditions it does not require scores to be calculated, for instance if a document falls in the range of two given timestamps. For all these Yes/No criteria, a filter clause is used.
Examples
Return all the results of a given index that falls between a date range:
GET my_index/_search
{
"query": {
"bool": {
"filter": {
"range": {
"created_at": {
"gte": "2020-01-01",
"lte": "2020-01-10"
}
}
}
}
}
}Notes
- Queries are used to find out how relevant a document is to a particular query by calculating a score for each document, whereas filters are used to match certain criteria and are cacheable to enable faster execution.
- Filters do not contribute to scoring and thus are faster to execute.
- There are major changes introduced in Elasticsearch version 2.x onward related to how query and filters are written and performed internally.
Common problems
- The most common problem with filters is incorrect use inside the query. If filters are not used correctly, query performance can be significantly affected. So filters must be used wherever there is scope of not calculating the score.
- Another problem often arises when using date range filters, if “now” is used to represent the current time. It has to be noted that “now” is continuously changing the timestamp and thus Elasticsearch cannot use caching of the response since the data set will keep changing.
Log Context
Log “failed to execute pipeline [{}]” classname is IngestActionFilter.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
}
void processIndexRequest(Task task; String action; ActionListener listener; ActionFilterChain chain; IndexRequest indexRequest) {
executionService.executeIndexRequest(indexRequest; t -> {
logger.error((Supplier>) () -> new ParameterizedMessage("failed to execute pipeline [{}]"; indexRequest.getPipeline()); t);
listener.onFailure(t);
}; success -> {
// TransportIndexAction uses IndexRequest and same action name on the node that receives the request and the node that
// processes the primary action. This could lead to a pipeline being executed twice for the same
// index request; hence we set the pipeline to null once its execution completed.
Find & fix Elasticsearch problems
