Briefly, this error occurs when Elasticsearch encounters an unexpected condition that prevents it from functioning correctly. This could be due to a variety of reasons such as incorrect configurations, insufficient resources, or software bugs. To resolve this issue, you can try the following: 1) Check the Elasticsearch logs for more detailed error messages. 2) Verify your configurations are correct. 3) Ensure that Elasticsearch has sufficient resources (CPU, memory, disk space). 4) Update Elasticsearch to the latest version to fix any potential software bugs.
This guide will help you check for common problems that cause the log ” Unexpected fatal internal error ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: repositories, plugin.
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 “Unexpected fatal internal error” class name is EncryptedRepository.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :
try {
computedRepositoryPasswordId = AESKeyUtils.computeId(
AESKeyUtils.generatePasswordBasedKey(repositoryPassword; masterRepositoryPasswordIdSalt)
);
} catch (Exception e) {
throw new RepositoryException(metadata.name(); "Unexpected fatal internal error"; e);
}
if (computedRepositoryPasswordId.equals(masterRepositoryPasswordId)) {
this.validatedLocalRepositoryPasswordHash = computedRepositoryPasswordId;
} else {
throw new RepositoryException(
[ratemypost]
