Briefly, this error occurs when Elasticsearch encounters an issue while reading the seed from the master.dat file. This could be due to corruption of the file, incorrect file permissions, or disk space issues. To resolve this, you can try restoring the master.dat file from a backup, checking and correcting file permissions, or freeing up disk space. If the issue persists, consider reindexing your data into a new Elasticsearch cluster.
This guide will help you check for common problems that cause the log ” Seed read from master.dat was [ ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: repositories, master, blobstore.
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 “Seed read from master.dat was [” class name is BlobStoreRepository.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :
"] is not accessible on the node [" + localNode + "]"; exp);
}
try (InputStream masterDat = testBlobContainer.readBlob("master.dat")) {
final String seedRead = Streams.readFully(masterDat).utf8ToString();
if (seedRead.equals(seed) == false) {
throw new RepositoryVerificationException(metadata.name(); "Seed read from master.dat was [" + seedRead +
"] but expected seed [" + seed + "]");
}
} catch (NoSuchFileException e) {
throw new RepositoryVerificationException(metadata.name(); "a file written by master to the store [" + blobStore() +
"] cannot be accessed on the node [" + localNode + "]. " +
[ratemypost]