# Shared Data-Store for multiple Nodes **URL:** \ **Category:** Elasticsearch\ **Created:** [February 18, 2020, 4:11pm UTC](https://discuss.elastic.co/t/shared-data-store-for-multiple-nodes/219832 "2020-02-18T16:11:26Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![KoettingSimon](https://avatars.discourse-cdn.com/v4/letter/k/ba9def/32.png) [@KoettingSimon](https://discuss.elastic.co/u/KoettingSimon)\ **Post date:** [February 18, 2020, 4:11pm UTC](https://discuss.elastic.co/t/shared-data-store-for-multiple-nodes/219832/1 "2020-02-18T16:11:26Z")
Hi All, At the moment we have 3 Elasticsearch-Node (All Master) Each Elasticsearch-Node is installed on a Ubuntu-VM on our central ESXi-Cluster. Each node has a dedicated /data mount to store the Data on a own volume in our SAN. The current default for our indices is 1 Replica. So i thought about one Central data-store for all nodes, so i could reduce the storage Size by the half because each shard is not stored 2x on different data-volumes. I found the setting for that in the documentation: [https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-node.html#max-local-storage-nodes](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-node.html#max-local-storage-nodes) So its possible and (at the moment) supported. But did "This setting is deprecated in 7.x and will be removed in version 8.0" mean that in 8.0 it wouldn't be supported anymore or just you don't need to set this attribute? And why its not recommend by Elastic, what are possible downsides? Thanks in Advice, Simon ---
**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:** [February 18, 2020, 4:23pm UTC](https://discuss.elastic.co/t/shared-data-store-for-multiple-nodes/219832/2 "2020-02-18T16:23:01Z")
> [@KoettingSimon](#): > > So i thought about one Central data-store for all nodes, so i could reduce the storage Size by the half because each shard is not stored 2x on different data-volumes. Your setup does not have that effect. If you have 1 replica (and 1 primary, obviously) then every shard is stored twice regardless of the underlying storage layout. > [@KoettingSimon](#): > > But did "This setting is deprecated in 7.x and will be removed in version 8.0" mean that in 8.0 it wouldn't be supported anymore or just you don't need to set this attribute? It won't be supported any more. Each node will require its own dedicated data path. > [@KoettingSimon](#): > > And why its not recommend by Elastic, what are possible downsides? If using `max_local_storage_nodes` then the relationship between nodes and their data depends on the order in which they start up and is therefore not well-defined. It's all too easy to end up with a cluster that cannot recover after a restart. ---
**Author:** ![KoettingSimon](https://avatars.discourse-cdn.com/v4/letter/k/ba9def/32.png) [@KoettingSimon](https://discuss.elastic.co/u/KoettingSimon)\ **Post date:** [February 18, 2020, 4:30pm UTC](https://discuss.elastic.co/t/shared-data-store-for-multiple-nodes/219832/3 "2020-02-18T16:30:01Z")
Hi David, Thanks for your reply. I forgot to write that I thought to reduce to 0 replicas because every node would have all data to use if one node goes offline. But if it wouldn't be supported anymore we won't change that😅 ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 17, 2020, 4:30pm UTC](https://discuss.elastic.co/t/shared-data-store-for-multiple-nodes/219832/4 "2020-03-17T16:30:02Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.