Encountered unexpected run state – How to solve related issues

Opster Team

Feb-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many 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.

This guide will help you check for common problems that cause the log ” Encountered unexpected run state ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: indexer and plugin.

Log Context

Log “[{}] Encountered unexpected run state [{}]” classname is TransformIndexer.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                return processChangedBuckets(agg);

                // Any other state is a bug; should not happen
                logger.warn("[{}] Encountered unexpected run state [{}]"; getJobId(); runState);
                throw new IllegalStateException("Transform indexer job encountered an illegal state [" + runState + "]");



Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content