# Changing index data location from work ro data **URL:** \ **Category:** Elasticsearch\ **Created:** [November 2, 2010, 8:42am UTC](https://discuss.elastic.co/t/changing-index-data-location-from-work-ro-data/3500 "2010-11-02T08:42:52Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [November 2, 2010, 8:42am UTC](https://discuss.elastic.co/t/changing-index-data-location-from-work-ro-data/3500/1 "2010-11-02T08:42:52Z")
Hi, The current location of the node(s) data resides under work/nodes/... . work also includes the location of the logs. The reason for this decision was because this data could have been transient with the shared gateway, and always recoverable. Though, even with shared gateway, this data will be reused usually there won't be a need for full recovery from gateway. ``` Because of that, the "work" location is inadequate. I want to create a ``` new location for data (indices). It will be named data and created in the same level as the work dir. There will be an option to change it using path.data. ``` In all other respects, it will be as if work was used. Meaning that ``` multi nodes will be supported in the same format as in work, as well as different cluster names. ``` What do you think? It will *require*, when upgrading to 0.13, to rename ``` work to data (if no explicit path is set), or reset the path if changed to use path.data (instead of path.work). -shay.banon ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 4:17am UTC](https://discuss.elastic.co/t/changing-index-data-location-from-work-ro-data/3500/2 "2017-07-06T04:17:19Z")