Could not find requested – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch is unable to locate the requested resource. This could be due to a missing index, document, or a plugin. To resolve this issue, you should first verify the existence of the requested resource. If it’s an index or document, ensure it’s correctly named and exists in your cluster. If it’s a plugin, ensure it’s properly installed. If the resource should exist but doesn’t, you may need to recreate it. If it shouldn’t exist, you may need to update your requests to remove references to it.

This guide will help you check for common problems that cause the log ” Could not find requested ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “Could not find requested” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 results = in.readList(hitReader);
 count = in.readLong();
 }  public static ResourceNotFoundException emptyQueryPage(ParseField resultsField) {
 return new ResourceNotFoundException("Could not find requested " + resultsField.getPreferredName());
 }  @Override
 public void writeTo(StreamOutput out) throws IOException {