Failed to write dangling indices state for index – 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 ” Failed to write dangling indices state for index ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: dangling, index and indices.

Log Context

Log “failed to write dangling indices state for index {}” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

             final long triggeredTimeMillis = threadPool.relativeTimeInMillis();
            try {
                danglingIndicesThreadPoolExecutor.execute(new AbstractRunnable() {
                    public void onFailure(Exception e) {
                        logger.warn(() -> new ParameterizedMessage("failed to write dangling indices state for index {}"; index); e);

                    protected void doRun() {
                        final boolean exists = danglingIndicesToWrite.remove(index);


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content