### Author:  [@Abhishek\_Shinde](https://discuss.elastic.co/u/Abhishek_Shinde)
#### Post date: [April 29, 2021, 6:01pm UTC](https://discuss.elastic.co/t/control-over-writing-data-to-a-specific-drive/271695/1 "2021-04-29T18:01:10Z")
We are planning to use single node Elasticsearch cluster. The node may contain multiple locations for writing indexing data.
I would like to know, if it is possible to write the data to a specific indexing location only?
For example, if there are 2 drives added in path.data namely C: & D: in a single node. Does elasticsearch provides a control to write the data to only C: drive?
Let me know if you've any idea how to achieve this.
---
### Author:  [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)
#### Post date: [April 29, 2021, 6:35pm UTC](https://discuss.elastic.co/t/control-over-writing-data-to-a-specific-drive/271695/2 "2021-04-29T18:35:51Z")
> [@Abhishek\_Shinde](#):
>
> The node may contain multiple locations for writing indexing data.
This functionality is deprecated and currently being removed, you probably shouldn't plan to use it:
>
>
> Multiple Data Paths (MDP) is a pseudo-software-RAID-0 feature within Elasticsear…ch allowing multiple paths to be specified in the path.data setting (which usually point to different disks). Although it has been used in the past as a simple way to run a multi-disk setups, it has long been a source of user complaints due to confusing or unintuitive behavior. Additionally, the implementation is complex, and not well-tested nor maintained, with practically no benefit over spanning the data path filesystem across multiple drives and/or running one node for each data path.
>
> We have long advised against using MDP, and are now ready to deprecate and remove it. This is a meta-issue to track that work.
>
> \- \[x\] Deprecate MDP in 7.13
> \- \[x\] Document migration path #71871
> \- \[\] ~Remove documentation from 8.0~
> \- \[\] ~Block MDP in 8.0~
> \- \[\] ~Remove MDP from 8.0~
> [@Abhishek\_Shinde](#):
>
> Let me know if you've any idea how to achieve this.
Use one node per path.
---
### Author:  [@Abhishek\_Shinde](https://discuss.elastic.co/u/Abhishek_Shinde)
#### Post date: [April 29, 2021, 6:53pm UTC](https://discuss.elastic.co/t/control-over-writing-data-to-a-specific-drive/271695/3 "2021-04-29T18:53:37Z")
Thanks for letting me it is going to depricate in the next release.
We are planning to host an elasticsearch cluster on a single virtual/physical machine. OS will be windows.
Can you please let me know, if we can deploy 2 nodes on a single cluster?
Please share if there are any documents around.
---
### Author:  [@Abhishek\_Shinde](https://discuss.elastic.co/u/Abhishek_Shinde)
#### Post date: [April 29, 2021, 7:07pm UTC](https://discuss.elastic.co/t/control-over-writing-data-to-a-specific-drive/271695/4 "2021-04-29T19:07:51Z")
Use one node per path.
Hi David,
If we can use only one drive then in case of disk full scenario, how can we move to another drive? What about the existing data?
Thanks
---
### Author:  [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)
#### Post date: [April 29, 2021, 7:52pm UTC](https://discuss.elastic.co/t/control-over-writing-data-to-a-specific-drive/271695/5 "2021-04-29T19:52:33Z")
Use one node per drive. If you want to move data off a drive, you can use [shard allocation filtering](https://www.elastic.co/guide/en/elasticsearch/reference/current/shard-allocation-filtering.html).
---
### Author:  [@Abhishek\_Shinde](https://discuss.elastic.co/u/Abhishek_Shinde)
#### Post date: [May 3, 2021, 7:11pm UTC](https://discuss.elastic.co/t/control-over-writing-data-to-a-specific-drive/271695/6 "2021-05-03T19:11:27Z")
Is there any mockups or documents available for "one node on path" design? Would like to know what all things one should consider during planning phase?
---
### Author:  [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)
#### Post date: [May 3, 2021, 7:52pm UTC](https://discuss.elastic.co/t/control-over-writing-data-to-a-specific-drive/271695/7 "2021-05-03T19:52:36Z")
I'm not sure what sort of documentation you might need. You configure one node for each data path, it really is that simple.
I thought I'd mentioned this above but it seems not: you can combine multiple drives together into a single data path using RAID-0 or similar. On Linux there are options like LVM too, not sure if there's a Windows equivalent to that. That's the simplest way to scale a node up as your needs grow.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [May 31, 2021, 7:53pm UTC](https://discuss.elastic.co/t/control-over-writing-data-to-a-specific-drive/271695/8 "2021-05-31T19:53:27Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.