Task isn’t running and hasn’t stored its results – How to solve this Elasticsearch error

Task isn’t running and hasn’t stored its results – 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 Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” task isn’t running and hasn’t stored its results ” 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: admin, node, task and cluster.

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 pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

Log”task [{}] isn’t running and hasn’t stored its results”classname  is TransportGetTaskAction.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

get.setParentTask(clusterService.localNode().getId(); thisTask.getId());
 
  client.get(get; ActionListener.wrap(r -> onGetFinishedTaskFromIndex(r; listener); e -> {
  if (ExceptionsHelper.unwrap(e; IndexNotFoundException.class) != null) {
  // We haven't yet created the index for the task results so it can't be found.
  listener.onFailure(new ResourceNotFoundException("task [{}] isn't running and hasn't stored its results"; e;
  request.getTaskId()));
  } else {
  listener.onFailure(e);
  }
  }));

 

Run the Check-Up to get a customized report like this:

Analyze your cluster