# Elasticsearch support for Distributed FS like Rook-ceph

**URL:** <https://discuss.elastic.co/t/elasticsearch-support-for-distributed-fs-like-rook-ceph/199410>\
**Category:** Elasticsearch\
**Created:** [September 13, 2019, 10:25am UTC](https://discuss.elastic.co/t/elasticsearch-support-for-distributed-fs-like-rook-ceph/199410 "2019-09-13T10:25:13Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**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:** [September 19, 2019, 3:30pm UTC](https://discuss.elastic.co/t/elasticsearch-support-for-distributed-fs-like-rook-ceph/199410/4 "2019-09-19T15:30:55Z")

</div>

It seems somewhat unnecessary since Elasticsearch already has distributed features built in. For instance, it natively scales out across multiple nodes, replicates its data, and automatically recovers from partial failures.

Remote storage also tends to have much higher latency than local disks, and this can have a big effect on performance.

Elasticsearch presents a particularly stressful workload to the filesystem and turns out to be rather good at hitting filesystem bugs and corner cases that other tests might have missed. This is true even of very mature and well-established filesystems. Distributed filesystems have seen much less production use and therefore seem a much riskier choice. See for instance this post with some links to recent `glusterfs` bugs:

> [@Underlying file changed by an external force](https://discuss.elastic.co/t/underlying-file-changed-by-an-external-force/137555/4):
>
> The first two Google hits for elasticsearch glusterfs lead to two serious-looking open GlusterFS issues that Elasticsearch triggers: [https://bugzilla.redhat.com/show\_bug.cgi?id=1390050](https://bugzilla.redhat.com/show_bug.cgi?id=1390050)[https://bugzilla.redhat.com/show\_bug.cgi?id=1379568](https://bugzilla.redhat.com/show_bug.cgi?id=1379568) This may be one of them, or may be something else, but it seems worth rethinking your setup. I don't think so. Both of the times I quoted are in UTC (note the trailing Z) and differ by 28 seconds, so it seems unlikely to be a timezone issue.

---

_[View the full topic](https://discuss.elastic.co/t/elasticsearch-support-for-distributed-fs-like-rook-ceph/199410)._
