Source indices have been deleted or closed. – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Source indices have been deleted or closed. ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: indices, source and plugin.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “Source indices have been deleted or closed.”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

ActionListener.wrap(r -> {
 try {
 final Aggregations aggregations = r.getAggregations();
 if (aggregations == null) {
 new ElasticsearchStatusException("Source indices have been deleted or closed."; RestStatus.BAD_REQUEST)
 final CompositeAggregation agg = aggregations.get(COMPOSITE_AGGREGATION_NAME);
 TransformIndexerStats stats = new TransformIndexerStats();


Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content