Export service is not started – 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 ” Export service is not started ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “Export service is not started”classname  is Exporters.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 * Exports a collection of monitoring documents using the configured exporters
 public void export(final Collection docs; final ActionListener listener) throws ExportException {
 if (this.lifecycleState() != Lifecycle.State.STARTED) {
 listener.onFailure(new ExportException("Export service is not started"));
 } else if (docs != null && docs.size() > 0) {
 wrapExportBulk(ActionListener.wrap(bulk -> {
 if (bulk != null) {
 doExport(bulk; docs; listener);
 } else {


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content