# Path.repo is not being updated by elasticsearch.yml file

**URL:** <https://discuss.elastic.co/t/path-repo-is-not-being-updated-by-elasticsearch-yml-file/344441>\
**Category:** Elasticsearch\
**Tags:** docker\
**Created:** [October 5, 2023, 5:53am UTC](https://discuss.elastic.co/t/path-repo-is-not-being-updated-by-elasticsearch-yml-file/344441 "2023-10-05T05:53:06Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Faker](https://avatars.discourse-cdn.com/v4/letter/f/eb9ed0/32.png) [@Faker](https://discuss.elastic.co/u/Faker)\
**Post date:** [October 5, 2023, 5:53am UTC](https://discuss.elastic.co/t/path-repo-is-not-being-updated-by-elasticsearch-yml-file/344441/1 "2023-10-05T05:53:06Z")

</div>

Hi, I'd like to thank you in advance for your reply.

i am going through hard tasks.  
our team use ES 7.13.12 and wants to migrate (& upgrade) to docker ELK 8.10.2

according to ES document, i should go through 7.17.13 before going to 8.10.2.  
so, i set up dockers for 7.17 and 8.10

my plan is to take snapshots on original ELK (v7.13.12)  
-\> then restore on ELK v7.17.13 (does this process reindex indices automatically??)  
--\> then take snapshots on ELK v7.17.13  
---\> then restore on ELK v8.10.2

restoring process went through **Restore an entire cluster**

**path.repo** defined in docker-compose.yml is well recognized  
i checked through below prompt

```auto
curl -k -u elastic:pwd -X GET https://localhost:PORT/_nodes/?pretty

```

```auto
"path" : {
          "logs" : "/usr/share/elasticsearch/logs",
          "home" : "/usr/share/elasticsearch",
          "repo" : [
            "/nas_data/es_backup/iddx"
          ]
        },

```

but **path.repo** that i typed inside elasticsearch.yml (inside docker container) is not recognized  
this is the line i added to elasticsearch.yml

```auto
path.repo: ["/nas_data/es_backup/iddx/", "/nas_data/es_backup/djtest"]

```

i restarted docker, checked authority of directory, but path.repo is not updated. ( iddx directory is what i wrote down in docker-compose.yml at first)

i searched through so much documents but i couldn't find solutions so please help me  
i saw some webpage about

```auto
java -version

```

but i'm not sure

---

<div class="post-metadata">

**Author:** ![HiteshSingh](https://avatars.discourse-cdn.com/v4/letter/h/f475e1/32.png) [@HiteshSingh](https://discuss.elastic.co/u/HiteshSingh)\
**Post date:** [October 5, 2023, 11:53am UTC](https://discuss.elastic.co/t/path-repo-is-not-being-updated-by-elasticsearch-yml-file/344441/2 "2023-10-05T11:53:35Z")

</div>

Are you following these documents for migration?

[Upgrade to Elastic 8.9.1 | Elastic Installation and Upgrade Guide [8.9] | Elastic ](https://www.elastic.co/guide/en/elastic-stack/8.9/upgrading-elastic-stack.html#prepare-to-upgrade)  
and  
[Upgrade Elasticsearch | Elastic Installation and Upgrade Guide [8.9] | Elastic](https://www.elastic.co/guide/en/elastic-stack/8.9/upgrading-elasticsearch.html)

What is the exact error are you getting? Please elaborate more.

---

<div class="post-metadata">

**Author:** ![Faker](https://avatars.discourse-cdn.com/v4/letter/f/eb9ed0/32.png) [@Faker](https://discuss.elastic.co/u/Faker)\
**Post date:** [October 6, 2023, 12:09am UTC](https://discuss.elastic.co/t/path-repo-is-not-being-updated-by-elasticsearch-yml-file/344441/3 "2023-10-06T00:09:17Z")

</div>

Thanks, but one of my question is that

even though i modified elasticsearch.yml inside docker-container,

```auto
root@09161caa83e4:/usr/share/elasticsearch/config# cat elasticsearch.yml
cluster.name: "docker-cluster"
network.host: 0.0.0.0
path.repo: ["/nas_data/es_backup/iddx", "/nas_data/es_backup/djtest"]

```

i got the error message "Cannot register new repository, failed to create repository

```auto
"Caused by: org.elasticsearch.repositories.RepositoryException: [ddd] location [/nas_data/es_backup/djtest] doesn't match any of the locations specified by path.repo",
"at org.elasticsearch.repositories.fs.FsRepository.<init>(FsRepository.java:112) ~[elasticsearch-7.17.13.jar:7.17.13]",
"at org.elasticsearch.repositories.RepositoriesModule.lambda$new$0(RepositoriesModule.java:45) ~[elasticsearch-7.17.13.jar:7.17.13]",
"at org.elasticsearch.repositories.Repository$Factory.create(Repository.java:66) ~[elasticsearch-7.17.13.jar:7.17.13]",
"at org.elasticsearch.repositories.RepositoriesService.createRepository(RepositoriesService.java:658) ~[elasticsearch-7.17.13.jar:7.17.13]",
"... 73 more"] }

```

of course i restarted docker, checked authentication of directory  
but it seems that the change doesn't take effect at all.

---

<div class="post-metadata">

**Author:** ![HiteshSingh](https://avatars.discourse-cdn.com/v4/letter/h/f475e1/32.png) [@HiteshSingh](https://discuss.elastic.co/u/HiteshSingh)\
**Post date:** [October 6, 2023, 1:55pm UTC](https://discuss.elastic.co/t/path-repo-is-not-being-updated-by-elasticsearch-yml-file/344441/4 "2023-10-06T13:55:45Z")

</div>

Are you running this in a cluster mode or as a single node? If in cluster mode, make sure all the nodes have same value of `path.repo`

Still if it doesn't work, try clearing your complete data and place the paths again and restart elastic.

---

<div class="post-metadata">

**Author:** ![Faker](https://avatars.discourse-cdn.com/v4/letter/f/eb9ed0/32.png) [@Faker](https://discuss.elastic.co/u/Faker)\
**Post date:** [October 10, 2023, 12:29am UTC](https://discuss.elastic.co/t/path-repo-is-not-being-updated-by-elasticsearch-yml-file/344441/5 "2023-10-10T00:29:57Z")

</div>

i have tested on both environment. (single node, multi node)

and i set-up new docker container so it does not contain any data.

so strange..

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [November 7, 2023, 12:30am UTC](https://discuss.elastic.co/t/path-repo-is-not-being-updated-by-elasticsearch-yml-file/344441/6 "2023-11-07T00:30:06Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
