Encountered a failure but indexer is STOPPED reason – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.4-8.9

Briefly, this error occurs when Elasticsearch tries to index data, but the indexer is in a stopped state. This could be due to a manual stop command, a crash, or a configuration issue. To resolve this, you can try restarting the indexer, checking the Elasticsearch logs for any issues that may have caused the indexer to stop, or reviewing your configuration settings to ensure they are correct. If the indexer was manually stopped, you can simply start it again. If it’s a crash, you might need to fix the underlying issue causing the crash.

This guide will help you check for common problems that cause the log ” [{}] encountered a failure but indexer is STOPPED; reason [{}]. ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, indexer.

Log Context

Log “[{}] encountered a failure but indexer is STOPPED; reason [{}].” classname is TransformTask.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

            // If we are stopped; this means that between the failure occurring and being handled; somebody called stop
            // We should just allow that stop to continue
            if (getIndexer() != null && getIndexer().getState() == IndexerState.STOPPED) {
                logger.info("[{}] encountered a failure but indexer is STOPPED; reason [{}]."; getTransformId(); reason);

            logger.error("[{}] transform has failed; experienced: [{}]."; transform.getId(); reason);