Component template matching request name not found – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.8-8.9

Briefly, this error occurs when Elasticsearch cannot find a component template that matches the name provided in the request. Component templates are used to define settings, mappings, and alias configurations for indices. The error suggests that the specified template does not exist. To resolve this issue, you can either create a new component template with the specified name or correct the name in your request if it was misspelled or incorrect. Also, ensure that the template is created in the correct cluster if you’re working with multiple Elasticsearch clusters.

This guide will help you check for common problems that cause the log ” component template matching [” + + “] not found ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: admin, template, indices, request.

Log Context

Log “component template matching [” + + “] not found” class name is 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 [" + + "] not found");  }
 if (request.includeDefaults() && DataLifecycle.isEnabled()) {