# Using RAID 0 vs multiple data paths after commit #10461

**URL:** <https://discuss.elastic.co/t/using-raid-0-vs-multiple-data-paths-after-commit-10461/855>\
**Category:** Elasticsearch\
**Created:** [May 18, 2015, 5:54pm UTC](https://discuss.elastic.co/t/using-raid-0-vs-multiple-data-paths-after-commit-10461/855 "2015-05-18T17:54:32Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![nik9000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nik9000/32/44947_2.png) [@nik9000](https://discuss.elastic.co/u/nik9000)\
**Post date:** [May 18, 2015, 9:46pm UTC](https://discuss.elastic.co/t/using-raid-0-vs-multiple-data-paths-after-commit-10461/855/4 "2015-05-18T21:46:32Z")

</div>

Its difficult. If one disk fails you lose everything on it and  
Elasticsearch gets upset until you shut down the service and remove the  
disk from its path.data and start it again. This is the best case scenario.  
As it is now I suspect it'll amount to the same thing as losing the whole  
RAID0 - the files on the other disk aren't super useful if you have  
replicas because they won't contain a full replica (until that commit you  
mention) and elasticsearch will have spun up a new replica when it noticed  
that that node was down anyway. It might have trouble noticing too.

If you have 2 disks in the system I'd go RAID0. If you have ten then RAID10

- though that is just my gut from relational db days. They hate RAID5/6. I  
suspect ES actually is less bad but I don't know how much.

---

_[View the full topic](https://discuss.elastic.co/t/using-raid-0-vs-multiple-data-paths-after-commit-10461/855)._