Pipeline id cannot have an empty on failure option defined – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when an Elasticsearch ingest pipeline is configured with an “on_failure” option, but no actions are defined for it. The “on_failure” option is used to specify what actions should be taken if an error occurs during processing. To resolve this issue, you can either remove the “on_failure” option if it’s not needed, or define at least one action for it. Actions could include logging the error, sending a notification, or attempting to process the data in a different way.

This guide will help you check for common problems that cause the log ” pipeline [” + id + “] cannot have an empty on_failure option defined ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: .

Log Context

Log “pipeline [” + id + “] cannot have an empty on_failure option defined” class name is Pipeline.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 + "] doesn't support one or more provided configuration parameters "
 + Arrays.toString(config.keySet().toArray())
 if (onFailureProcessorConfigs != null && onFailureProcessors.isEmpty()) {
 throw new ElasticsearchParseException("pipeline [" + id + "] cannot have an empty on_failure option defined");
 CompoundProcessor compoundProcessor = new CompoundProcessor(false; processors; onFailureProcessors);
 return new Pipeline(id; description; version; metadata; compoundProcessor);


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?