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 Error Check-Up which analyzes 2 JSON files to detect many configuration 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 ” 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.

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);
 return new Pipeline(id; description; version; compoundProcessor);


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content