# ElastiSearch Supports GlusterFS and Rook Storage System?

**URL:** <https://discuss.elastic.co/t/elastisearch-supports-glusterfs-and-rook-storage-system/193319>\
**Category:** Elasticsearch\
**Created:** [August 1, 2019, 12:39pm UTC](https://discuss.elastic.co/t/elastisearch-supports-glusterfs-and-rook-storage-system/193319 "2019-08-01T12:39:53Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [August 1, 2019, 12:52pm UTC](https://discuss.elastic.co/t/elastisearch-supports-glusterfs-and-rook-storage-system/193319/2 "2019-08-01T12:52:38Z")

</div>

We don't run any tests against either of those systems, and generally recommend to use local storage instead of network-attached storage for performance reasons. Past versions of GlusterFS are known to cause corruptions in Elasticsearch indices - for example:

> [@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/elastisearch-supports-glusterfs-and-rook-storage-system/193319)._