A primary endpoint is required when setting a secondary endpoint – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 8.8-8.9

Briefly, this error occurs when a secondary endpoint is set in Elasticsearch without setting a primary endpoint. Elasticsearch requires a primary endpoint to function properly, and a secondary endpoint can only be set if a primary one is already in place. To resolve this issue, ensure that a primary endpoint is set before setting a secondary one. Alternatively, you can remove the secondary endpoint if it’s not necessary. Also, check your configuration files or settings to ensure the primary endpoint is correctly defined and accessible.

This guide will help you check for common problems that cause the log ” A primary endpoint is required when setting a secondary endpoint ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: azure, repository-azure, repositories.

Log Context

Log “A primary endpoint is required when setting a secondary endpoint” class name is AzureStorageSettings.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 if (hasEndpointSuffix && hasSecondaryEndpoint) {
 throw new SettingsException("Both an endpoint suffix as well as a secondary endpoint were set");
 }  if (hasEndpoint == false && hasSecondaryEndpoint) {
 throw new SettingsException("A primary endpoint is required when setting a secondary endpoint");
 }  if (hasEndpointSuffix) {
 connectionStringBuilder.append(";EndpointSuffix=").append(endpointSuffix);
 }

 

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?