Pipeline ” + id + ” cannot have an empty on_failure option defined – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Check-Up which can resolve issues that cause many errors.

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: ,,, and.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

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

if (config.isEmpty() == false) {
 throw new ElasticsearchParseException("pipeline [" + id +
 "] 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; Collections.unmodifiableList(processors);
 Collections.unmodifiableList(onFailureProcessors));
 return new Pipeline(id; description; version; compoundProcessor);
 }

 

Try AutoOps to detect and fix issues in your cluster:

Analyze Your Cluster

Skip to content