Briefly, this error occurs when there is a configuration issue in Elasticsearch where both an endpoint suffix and a secondary endpoint are set simultaneously. This is not allowed as it can cause conflicts in routing requests. To resolve this issue, you can either remove the endpoint suffix or the secondary endpoint from your configuration. Ensure that only one is set at a time. Alternatively, you can check your application’s code to ensure it’s not setting both parameters simultaneously.
This guide will help you check for common problems that cause the log ” Both an endpoint suffix as well as a secondary endpoint were set ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: azure, repository-azure, repositories.
Overview
An Elasticsearch snapshot provides a backup mechanism that takes the current state and data in the cluster and saves it to a repository (read snapshot for more information). The backup process requires a repository to be created first. The repository needs to be registered using the _snapshot endpoint, and multiple repositories can be created per cluster. The following repository types are supported:
Repository types
| Repository type | Configuration type |
|---|---|
| Shared file system | Type: “fs” |
| S3 | Type : “s3” |
| HDFS | Type :“hdfs” |
| Azure | Type: “azure” |
| Google Cloud Storage | Type : “gcs” |
Examples
To register an “fs” repository:
PUT _snapshot/my_repo_01
{
"type": "fs",
"settings": {
"location": "/mnt/my_repo_dir"
}
}Notes and good things to know
- S3, HDFS, Azure and Google Cloud require a relevant plugin to be installed before it can be used for a snapshot.
- The setting, path.repo: /mnt/my_repo_dir needs to be added to elasticsearch.yml on all the nodes if you are planning to use the repo type of file system. Otherwise, it will fail.
- When using remote repositories, the network bandwidth and repository storage throughput should be high enough to complete the snapshot operations normally, otherwise you will end up with partial snapshots.
Log Context
Log “Both an endpoint suffix as well as a secondary endpoint were set” class name is AzureStorageSettings.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :
if (hasEndpointSuffix && hasEndpoint) {
throw new SettingsException("Both an endpoint suffix as well as a primary endpoint were set");
} 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");
}
