# Mulitple paths in path.data - upgrade issue

**URL:** <https://discuss.elastic.co/t/mulitple-paths-in-path-data-upgrade-issue/47404>\
**Category:** Elasticsearch\
**Created:** [April 14, 2016, 2:42pm UTC](https://discuss.elastic.co/t/mulitple-paths-in-path-data-upgrade-issue/47404 "2016-04-14T14:42:00Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Marjana](https://avatars.discourse-cdn.com/v4/letter/m/6a8cbe/32.png) [@Marjana](https://discuss.elastic.co/u/Marjana)\
**Post date:** [April 14, 2016, 2:42pm UTC](https://discuss.elastic.co/t/mulitple-paths-in-path-data-upgrade-issue/47404/1 "2016-04-14T14:42:00Z")

</div>

Hi,  
We are running on 1.7 and plan to upgrade to 2.2. Our path.data has 2 directories in it. In testing upgrade, it took 10+hours to complete the upgrade of 8 data nodes with 1TB of data.  
I read about 2.0 breaking change when it needs to move all the files belonging to the same shard to the same path.  
I was thinking we could go back to using 1 path temporarily (plenty of space, using only 1% disk on each path), while we are in 1.7. Then upgrade in timely fashion, and then add the other path.  
How would we go about changing path.data from 2 directories in 1 while on 1.7? Am I looking at the same process of 10+ hours of moving files around? Is there some workaround?  
Thanks

---

<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:** [July 5, 2017, 10:59pm UTC](https://discuss.elastic.co/t/mulitple-paths-in-path-data-upgrade-issue/47404/2 "2017-07-05T22:59:11Z")

</div>


