Snapshot - Register repository for Snapshot

[Prabakar]

Hello Team,

We are using Elastic on Kubernetes (ECK) with elastic Enterprise license. We have created on- premise elastic clusters. We are trying to create repository to take snapshots, but we are getting below error while firing below API.

PUT /_snapshot/nfs-server
{
"type": "fs",
"settings": {
"location": "/path/",
"compress": true
}
}

{
"error" : {
"root_cause" : [
{
"type" : "repository_exception",
"reason" : "[nfs-server] location [/osl_nonprod_car7598_nodr_pr/] doesn't match any of the locations specified by path.repo because this setting is empty"
}
],
"type" : "repository_exception",
"reason" : "[nfs-server] failed to create repository",
"caused_by" : {
"type" : "repository_exception",
"reason" : "[nfs-server] location [/path/] doesn't match any of the locations specified by path.repo because this setting is empty"
}
},
"status" : 500
}

It says we need to add path.repo property on yml files of each node. But we are using ECK and we use YAML files for the deployments. Still do I need to add path.repo on all the nodes? Please share your thoughts.

[casterQ (caster)]

when you use nfs as your snapshot repository，you need to ：

1. mount the file system to the same location on all master and data nodes.
2. Then add the file system’s path or parent directory to the path.repo setting in elasticsearch.yml for each master and data node

[Prabakar]

1. Do I need to add path.repo setting in Elasticsearch.yml for ECK (Elastic on Kubernetes ) environment as well? We have not done that for ECK on GCP (Google eCloud) environment.

2. We are using coordinating nodes as well. Do we need to add path.repo on coordinating yml files as well?

[leandrojmp (Leandro Pereira)]

You need to add path.repo in the elasticsearch.yml file for all data and master nodes, and all of those nodes need to have the same path mounted.

I'm not sure how you will do that with ECK, but every data and master node needs to have this config.

The documentation does not say anything about the need to have path.repo on coordinating nodes, if they are not data and master nodes as well, you can leave this config out for coordinating nodes.