# ES data on Glusterfs **URL:** \ **Category:** Elasticsearch\ **Created:** [December 18, 2013, 12:34am UTC](https://discuss.elastic.co/t/es-data-on-glusterfs/14922 "2013-12-18T00:34:07Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Josh\_Harrison](https://avatars.discourse-cdn.com/v4/letter/j/0ea827/32.png) [@Josh\_Harrison](https://discuss.elastic.co/u/Josh_Harrison)\ **Post date:** [December 18, 2013, 12:34am UTC](https://discuss.elastic.co/t/es-data-on-glusterfs/14922/1 "2013-12-18T00:34:07Z")
Is it a dumb idea to have my ES data directory on a glusterFS/lusterfS storage node? Because we've got some BIG data that we'd like to index, but it's too big for the local storage on our test cluster. -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/11c1be2e-a908-454e-92b5-e65f90e33156%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/11c1be2e-a908-454e-92b5-e65f90e33156%40googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [December 18, 2013, 1:58am UTC](https://discuss.elastic.co/t/es-data-on-glusterfs/14922/2 "2013-12-18T01:58:39Z")
Use Gluster on its native protocol, not on NFS and the like. If you want backup/restore, Gluster support was announced as a post 1.0 ES feature. Jörg -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAKdsXoGcB0OvxWr48L%2BwSJ3EgBdXnxbYaaSezA%3Dzw-ahQbYvdw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoGcB0OvxWr48L%2BwSJ3EgBdXnxbYaaSezA%3Dzw-ahQbYvdw%40mail.gmail.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Josh\_Harrison](https://avatars.discourse-cdn.com/v4/letter/j/0ea827/32.png) [@Josh\_Harrison](https://discuss.elastic.co/u/Josh_Harrison)\ **Post date:** [December 18, 2013, 2:02am UTC](https://discuss.elastic.co/t/es-data-on-glusterfs/14922/3 "2013-12-18T02:02:12Z")
Cool, thanks. It looks like I've conflated gluster and lustre which are unfortunately totally unrelated. We're running lustre. On Tuesday, December 17, 2013 5:58:39 PM UTC-8, Jörg Prante wrote: > Use Gluster on its native protocol, not on NFS and the like. > > If you want backup/restore, Gluster support was announced as a post 1.0 ES > feature. > > Jörg -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/212a220f-33eb-4026-9454-1d4b84e2ad17%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/212a220f-33eb-4026-9454-1d4b84e2ad17%40googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [December 18, 2013, 2:25am UTC](https://discuss.elastic.co/t/es-data-on-glusterfs/14922/4 "2013-12-18T02:25:21Z")
Same with Lustre. Do not use it over the network, because then it is slow. Also, with ES replica shards and local gateway with recovery over the network, you have a mechanism similar to what you can achieve with Lustre, so there is not much sense in duplicating it. YMMV. Just my 2p. Jörg -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAKdsXoH8e8N0y6j97STL2NWFd-QC%2B4wx7Q3ea-%2BRGs-vYuK-FA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoH8e8N0y6j97STL2NWFd-QC%2B4wx7Q3ea-%2BRGs-vYuK-FA%40mail.gmail.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Abhijit\_Paul](https://avatars.discourse-cdn.com/v4/letter/a/8e8cbc/32.png) [@Abhijit\_Paul](https://discuss.elastic.co/u/Abhijit_Paul)\ **Post date:** [May 6, 2017, 6:45pm UTC](https://discuss.elastic.co/t/es-data-on-glusterfs/14922/5 "2017-05-06T18:45:25Z")
@Josh_Harrison @jprante Hello folks, I am trying out to setup for "ES data on Glusterfs" but facing issues like, "[CorruptIndexException](https://bugzilla.redhat.com/show_bug.cgi?id=1390050)", and due to that ES index health trued RED, cache consistency issue and [Openshift Logging ElasticSearch FSLocks when using GlusterFS storage backend](https://bugzilla.redhat.com/show_bug.cgi?id=1426548) All this issue are facing with glusterfs 3.10.1 version. Any pointers or forwards will be appreciated. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 10:00pm UTC](https://discuss.elastic.co/t/es-data-on-glusterfs/14922/6 "2017-07-05T22:00:30Z")