Briefly, this error occurs when Elasticsearch is unable to load the default project ID, which is usually due to incorrect configuration settings or missing project ID in the Elasticsearch configuration file. To resolve this issue, you can check the Elasticsearch configuration file and ensure that the default project ID is correctly set. If the project ID is missing, you should add it. Also, ensure that Elasticsearch has the necessary permissions to access and read the configuration file. Lastly, restarting the Elasticsearch service after making these changes can help in resolving the issue.
This guide will help you check for common problems that cause the log ” failed to load default project id ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: repository-gcs, 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 “failed to load default project id” classname is GoogleCloudStorageService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
defaultProjectId = SocketAccess.doPrivilegedIOException(ServiceOptions::getDefaultProjectId);
if (defaultProjectId != null) {
storageOptionsBuilder.setProjectId(defaultProjectId);
}
} catch (Exception e) {
logger.warn("failed to load default project id"; e);
}
if (defaultProjectId == null) {
try {
// fallback to manually load project ID here as the above ServiceOptions method has the metadata endpoint hardcoded;
// which makes it impossible to test
