Cannot find in descriptor – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.15

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when Elasticsearch is unable to locate a specific index or type in the descriptor. This could be due to a typo in the index or type name, or the index or type may not exist in the Elasticsearch cluster. To resolve this issue, you can verify the index or type name for any typos, ensure the index or type exists in the cluster, or create the index or type if it does not exist.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” Cannot find [{}]/[{}] in descriptor [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “Cannot find [{}]/[{}] in descriptor [{}]” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 }  private String getIdpLocation() {
 final String location = getIdentityProviderEndpoint(idpBinding; IDPSSODescriptor::getSingleSignOnServices);
 if (location == null) {
 throw new ElasticsearchException("Cannot find [{}]/[{}] in descriptor [{}]";
 IDPSSODescriptor.DEFAULT_ELEMENT_NAME; idpBinding; identityProvider.getID());
 return location;


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?