Updated: Jan-20
Elasticsearch Version: 1.7-8.0
Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which can resolve issues causing many log errors (free and no installation required)
This guide will help you check for common problems that cause the log “Failed to execute pipeline for a bulk request” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: bulk, request.
Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to discover the cause of many errors and provides suitable actionable recommendations.
Bulk in Elasticsearch
What it is
In Elasticsearch, when using the Bulk API it is possible to perform many write operations in a single API call, which increases the indexing speed. Using the Bulk API is more efficient than sending multiple, separate requests. This can be done for the following four actions:
Examples
The bellow bulk request will index a document, delete another document, and update an existing document.
POST _bulk
{ "index" : { "_index" : "myindex", "_id" : "1" } }
{ "field1" : "value" }
{ "delete" : { "_index" : “myindex", "_id" : "2" } }
{ "update" : {"_id" : "1", "_index" : "myindex"} }
{ "doc" : {"field2" : "value5"} }
Notes
- Bulk API is useful when you need to index data streams that can be queued up and indexed in batches of hundreds or thousands, such as logs.
- There is no correct number of actions or limits to perform on a single bulk call, but you will need to figure out the optimum number by experimentation, given the cluster size, number of nodes, hardware specs etc.
Log Context
Log”Failed to execute pipeline for a bulk request” classname is TransportBulkAction.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
logger.debug(() -> new ParameterizedMessage("failed to execute pipeline [{}] for document [{}/{}/{}]";
indexRequest.getPipeline(); indexRequest.index(); indexRequest.type(); indexRequest.id()); exception);
bulkRequestModifier.markCurrentItemAsFailed(exception);
}; (exception) -> {
if (exception != null) {
logger.error("failed to execute pipeline for a bulk request"; exception);
listener.onFailure(exception);
} else {
long ingestTookInMillis = TimeUnit.NANOSECONDS.toMillis(System.nanoTime() - ingestStartTimeInNanos);
BulkRequest bulkRequest = bulkRequestModifier.getBulkRequest();
ActionListener actionListener = bulkRequestModifier.wrapActionListenerIfNeeded(ingestTookInMillis;
Related issues to this log
We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :
1 Performance Issue: rejected execution of org.elasticsearch.ingest.PipelineExecutionSService -views 0.42 K ,score –
2 Failed To Execute Pipeline For A Bu
About Opster
Opster provides real-time recommendations to resolve and prevent Elasticsearch problems and can perform advanced actions that improve performance, automate operation and reduces costs
