Importing dangled indices from – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.11-8.9

Briefly, this error occurs when Elasticsearch discovers indices that are not associated with any cluster state. These are known as “dangled” indices. They usually appear due to a failed deletion or a cluster recovery. To resolve this issue, you can either manually delete the dangled indices from the data directory or set the ‘gateway.auto_import_dangled_indices’ to ‘no’ to prevent automatic import. Alternatively, you can set it to ‘closed’ to import the dangled indices but keep them closed until manually opened.

This guide will help you check for common problems that cause the log ” importing dangled indices {} from [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: indices, dangled.

Log Context

Log “importing dangled indices {} from [{}]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                    if (importNeeded == false) {
                        return currentState;
          "importing dangled indices {} from [{}]"; sb.toString(); request.fromNode);

                    RoutingTable routingTable =;
                    ClusterState updatedState = ClusterState.builder(currentState)


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?