Source indices have been deleted or closed. – Elasticsearch Error How To Solve Related Issues



Source indices have been deleted or closed. – Elasticsearch Error How To Solve Related Issues

Updated: July-20

Elasticsearch Version: 1.7-8.0

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

 

This guide will help you check for common problems that cause the log “Source indices have been deleted or closed.” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: indices, source, plugin.


Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to discover the cause of many errors and provides suitable actionable recommendations (free tool that requires no installation). 

Log Context

Log”Source indices have been deleted or closed.”classname  is TransportPreviewTransformAction.java
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) {
  listener.onFailure(
  new ElasticsearchStatusException("Source indices have been deleted or closed."; RestStatus.BAD_REQUEST)
  );
  return;
  }
  final CompositeAggregation agg = aggregations.get(COMPOSITE_AGGREGATION_NAME);
  TransformIndexerStats stats = new TransformIndexerStats();

Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Removing Data From ElasticSearch -views 554,347 ,score 366

how to rename an index in a cluster? -views   104,006,score 110



Find Configuration Errors

Analyze Now