# Elasticsearch shard unassigned and changed to red

**URL:** https://discuss.elastic.co/t/elasticsearch-shard-unassigned-and-changed-to-red/137729
**Category:** Elasticsearch
**Created:** [June 28, 2018, 5:01am UTC](https://discuss.elastic.co/t/elasticsearch-shard-unassigned-and-changed-to-red/137729 "2018-06-28T05:01:48Z")
**Posts on this page:** 1
**Showing post:** 6

<div class="post-metadata">

### Author: ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [June 29, 2018, 7:35am UTC](https://discuss.elastic.co/t/elasticsearch-shard-unassigned-and-changed-to-red/137729/6 "2018-06-29T07:35:10Z")

</div>

That is a very small heap for running Elasticsearch, but should not cause corruption. The reason I am asking about the storage is that some types of storage do not work with Elasticsearch, and can cause corruption. See these posts for an 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.

> [@Elk on Docker Swarm and glusterFS crash](https://discuss.elastic.co/t/elk-on-docker-swarm-and-glusterfs-crash/127940):
>
> Hi, I'm trying to deploy an ELK stack on docker swarm. If I bind the elastic dir data to a Docker volume there is no problem. The problems comes as soon as I try to bind the elstastic data dir to a glusterFS volume. I use glusterFS to synchronise the data between all the swarm nodes in the cluster. I deploy ELK using the following code: elasticsearch: image: docker.elastic.co/elasticsearch/elasticsearch:6.2.3 # container\_name: elasticsearch environment: - "http.host=0.0.…

---

_[View the full topic](https://discuss.elastic.co/t/elasticsearch-shard-unassigned-and-changed-to-red/137729)._
