# Removed MDP (Multi Data path) how to configure new

**URL:** <https://discuss.elastic.co/t/removed-mdp-multi-data-path-how-to-configure-new/276467>\
**Category:** Elasticsearch\
**Created:** [June 20, 2021, 7:28pm UTC](https://discuss.elastic.co/t/removed-mdp-multi-data-path-how-to-configure-new/276467 "2021-06-20T19:28:05Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![elasticforme](https://avatars.discourse-cdn.com/v4/letter/e/f05b48/32.png) [@elasticforme](https://discuss.elastic.co/u/elasticforme)\
**Post date:** [June 20, 2021, 7:28pm UTC](https://discuss.elastic.co/t/removed-mdp-multi-data-path-how-to-configure-new/276467/1 "2021-06-20T19:28:05Z")

</div>

Now that I just learned that Elk is removing MDP that means I won't be assign multiple raw disk. 😭 ( which is bad idea)

but now it is there how do I configure. which is step back.

if I use raid1 then I am loosing half  
if I use raid0 I have no fail safe whatever  
if I use riid5, 6 loosing disk and speed.

what are people generally using for data path?

I have 4x2TB NVME in a data node and using /data01, /data02, /data03, /data04 at this time.

---

<div class="post-metadata">

**Author:** ![BenB196](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/benb196/32/83401_2.png) [@BenB196](https://discuss.elastic.co/u/BenB196)\
**Post date:** [June 20, 2021, 9:48pm UTC](https://discuss.elastic.co/t/removed-mdp-multi-data-path-how-to-configure-new/276467/2 "2021-06-20T21:48:49Z")

</div>

I'd say you have three options:

1. Use RAID0 with a single Elasticsearch instance.
  1. Elastic from what I can tell recommends the use of RAID0, when using RAID, as data resiliency/redundancy is intended to be handled at the application layer via replicas + allocation awareness.

2. Split the CPU and RAM resources the your existing Elasticsearch instance uses by 4, then run 4 instances of Elasticsearch on the same node.
  1. This can most easily be achieved by using containers (either via Docker or [Kubernetes](https://www.elastic.co/guide/en/cloud-on-k8s/current/index.html))

3. You could also split it by two (2) and have two (2) RAID 0 arrays with two (2) instances of Elasticsearch each using one (1). Though this would be mixing both options 1 and 2, and probably adds unneeded complication/management overhead.

If you were to provide your reasoning behind using multi-path currently, it might help in providing a more accurate/useful solution.

---

<div class="post-metadata">

**Author:** ![elasticforme](https://avatars.discourse-cdn.com/v4/letter/e/f05b48/32.png) [@elasticforme](https://discuss.elastic.co/u/elasticforme)\
**Post date:** [June 20, 2021, 10:34pm UTC](https://discuss.elastic.co/t/removed-mdp-multi-data-path-how-to-configure-new/276467/3 "2021-06-20T22:34:29Z")

</div>

What I like about using multi-path is all the disk is being used and full i/o achieved.  
if I loose one disk I only have 1/4 of shard unavailable untill I replace the a disk.

performance is what I am after. and seems like you have good suggestion, I didn't thought about 2nd 3rd option at all.

was only thinking how I can setup raid 🙂

each data node has 98 gig ram, and on 10 gig network.

---

<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 18, 2021, 10:34pm UTC](https://discuss.elastic.co/t/removed-mdp-multi-data-path-how-to-configure-new/276467/4 "2021-07-18T22:34:34Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.