Briefly, this error occurs when both an endpoint suffix and a primary endpoint are configured in Elasticsearch. This is a configuration issue, as Elasticsearch expects only one of these to be set. To resolve this, you can either remove the endpoint suffix or the primary endpoint from your configuration. Make sure to keep the one that is necessary for your specific use case. Also, ensure that the remaining endpoint is correctly configured to avoid further issues.
This guide will help you check for common problems that cause the log ” Both an endpoint suffix as well as a primary 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 primary endpoint were set” class name is AzureStorageSettings.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :
final boolean hasEndpointSuffix = Strings.hasText(endpointSuffix);
final boolean hasEndpoint = Strings.hasText(endpoint);
final boolean hasSecondaryEndpoint = Strings.hasText(secondaryEndpoint); 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");
}
