# Elasticsearch shards are UNASSIGNED CLUSTER\_RECOVERED after I changed path.data **URL:** \ **Category:** Elasticsearch\ **Created:** [October 23, 2017, 9:02am UTC](https://discuss.elastic.co/t/elasticsearch-shards-are-unassigned-cluster-recovered-after-i-changed-path-data/104871 "2017-10-23T09:02:16Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![daaakeee](https://avatars.discourse-cdn.com/v4/letter/d/dbc845/32.png) [@daaakeee](https://discuss.elastic.co/u/daaakeee)\ **Post date:** [October 23, 2017, 9:02am UTC](https://discuss.elastic.co/t/elasticsearch-shards-are-unassigned-cluster-recovered-after-i-changed-path-data/104871/1 "2017-10-23T09:02:16Z")
Hi all. I need help here, I wanted to change path.data settings in elasticsearch.yml and now I have 78 shards UNASSIGNED CLUSTER\_RECOVERED. What can I do to recover my data? ---
**Author:** ![Bernt\_Rostad](https://avatars.discourse-cdn.com/v4/letter/b/3ab097/32.png) [@Bernt\_Rostad](https://discuss.elastic.co/u/Bernt_Rostad)\ **Post date:** [October 23, 2017, 9:34am UTC](https://discuss.elastic.co/t/elasticsearch-shards-are-unassigned-cluster-recovered-after-i-changed-path-data/104871/2 "2017-10-23T09:34:12Z")
Did you remember to rename / move the directory on the file system, matching the new path.data setting, before starting up Elasticsearch again? If not, you should stop Elasticsearch, rename the directory and then try to start up Elasticsearch again. I've only done this once myself but I had no problems after the change of data.path. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 20, 2017, 9:34am UTC](https://discuss.elastic.co/t/elasticsearch-shards-are-unassigned-cluster-recovered-after-i-changed-path-data/104871/3 "2017-11-20T09:34:21Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.