# Storage Shared or local **URL:** \ **Category:** Elasticsearch\ **Created:** [July 29, 2019, 5:51am UTC](https://discuss.elastic.co/t/storage-shared-or-local/192604 "2019-07-29T05:51:03Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![msk\_76](https://avatars.discourse-cdn.com/v4/letter/m/dbc845/32.png) [@msk\_76](https://discuss.elastic.co/u/msk_76)\ **Post date:** [July 29, 2019, 5:51am UTC](https://discuss.elastic.co/t/storage-shared-or-local/192604/1 "2019-07-29T05:51:03Z")
I am planning to setup a 3 node ES cluster with all 3 nodes have their local disk storage for data and NFS storage for ES install in following fashion of storage in given filesystem names Node[1,2,3] : /NFS/install Node1 : /local1/data Node2 : /local2/data Node3 : /local3/data Shard Setup : 2 primary and 1 replica for each index. The above local filesystem of each node are not shared with other 2 nodes i.e. Node2 can't read data on /local1/data(Node1) or /local3/data(Node3). /NFS/install is a common NFS filesystem mounted on all above 3 nodes which contain ES installation package with following directories bin config data lib LICENSE.txt logs modules NOTICE.txt plugins README.textile script How to set the path.data at cluster level for above data & install storage filesystem naming? Should I do some renaming of local filesystem names to simplify? ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [July 29, 2019, 1:10pm UTC](https://discuss.elastic.co/t/storage-shared-or-local/192604/2 "2019-07-29T13:10:36Z")
> [@msk\_76](#): > > Should I do some renaming of local filesystem names to simplify? No, you should at least give each node its own config directory, and then you can set per-node options like the data path on a node-by-node basis. Sharing a config directory between nodes will be very confusing. ---
**Author:** ![msk\_76](https://avatars.discourse-cdn.com/v4/letter/m/dbc845/32.png) [@msk\_76](https://discuss.elastic.co/u/msk_76)\ **Post date:** [July 30, 2019, 5:11am UTC](https://discuss.elastic.co/t/storage-shared-or-local/192604/3 "2019-07-30T05:11:00Z")
Ok. So keeping a independent copy of config(elasticsearch.yml) for each node will not cause an issue in case this file gets deleted or modified in a running cluster? Does ES maintains a meta information of these node specific yml files within database? ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [July 30, 2019, 6:01am UTC](https://discuss.elastic.co/t/storage-shared-or-local/192604/4 "2019-07-30T06:01:42Z")
> [@msk\_76](#): > > Ok. So keeping a independent copy of config(elasticsearch.yml) for each node will not cause an issue in case this file gets deleted or modified in a running cluster? Elasticsearch reads its config at startup, so will not notice any modifications or deletions until the next time it starts. Except the [keystore](https://www.elastic.co/guide/en/elasticsearch/reference/current/secure-settings.html), which Elasticsearch can reload while it is running. > [@msk\_76](#): > > Does ES maintains a meta information of these node specific yml files within database? No. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 27, 2019, 6:01am UTC](https://discuss.elastic.co/t/storage-shared-or-local/192604/5 "2019-08-27T06:01:43Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.