Component template matching ” + request.name() + ” not found – How to solve this Elasticsearch error

Average Read Time

2 Mins

Component template matching ” + request.name() + ” not found – 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 ” component template matching ” + request.name() + ” not found ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: admin, request, template and indices.

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 “component template matching [” + request.name() + “] not found”classname  is TransportGetComponentTemplateAction.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

}
 }
 } else if (allTemplates.containsKey(name)) {
 results.put(name; allTemplates.get(name));
 } else {
 throw new ResourceNotFoundException("component template matching [" + request.name() + "] not found");
 } 
 listener.onResponse(new GetComponentTemplateAction.Response(results));
 }
 }

 

Watch a demo of the Check-Up:

Analyze your cluster

Skip to content