Briefly, this error occurs when Elasticsearch finds 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 hard shutdown. To resolve this issue, you can manually delete these dangled indices if they are not needed. Alternatively, you can import them manually if they contain important data. Also, ensure to have a proper shutdown process to avoid such issues in the future. Regular monitoring and maintenance of the Elasticsearch cluster can also help prevent this error.
This guide will help you check for common problems that cause the log ” auto importing dangled indices {} from [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: dangled, indices.
Log Context
Log “auto importing dangled indices {} from [{}]” classname is LocalAllocateDangledIndices.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
.append("]");
}
if (!importNeeded) {
return currentState;
}
logger.info("auto importing dangled indices {} from [{}]"; sb.toString(); request.fromNode);
RoutingTable routingTable = routingTableBuilder.build();
ClusterState updatedState = ClusterState.builder(currentState).metadata(metadata).blocks(blocks)
.routingTable(routingTable).build();
