# Mysterious "red" cluster status has happened ~4x now

**URL:** <https://discuss.elastic.co/t/mysterious-red-cluster-status-has-happened-4x-now/12226>\
**Category:** Elasticsearch\
**Created:** [June 2, 2013, 3:33pm UTC](https://discuss.elastic.co/t/mysterious-red-cluster-status-has-happened-4x-now/12226 "2013-06-02T15:33:20Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![inZania](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/inzania/32/2305_2.png) [@inZania](https://discuss.elastic.co/u/inZania)\
**Post date:** [June 2, 2013, 3:33pm UTC](https://discuss.elastic.co/t/mysterious-red-cluster-status-has-happened-4x-now/12226/1 "2013-06-02T15:33:20Z")

</div>

Every few weeks, my ElasticSearch nodes suddenly take on a "red" status. This is on my production servers and I rely heavily on ES, and the only solution I've been able to come up with is to delete all the data and restart ElasticSearch (which sucks, needless to say). Simply restarting ES doesn't work:

```
# curl http://localhost:9200/_cluster/health
{"cluster_name":"streamified","status":"red","timed_out":false,"number_of_nodes":2,"number_of_data_nodes":2,"active_primary_shards":10,"active_shards":20,"relocating_shards":0,"initializing_shards":0,"unassigned_shards":10}
```

I'm hoping someone can help me make sense of the logs; they're a mystery to me. I'm running 2 ElasticSearch machines with 4GB of RAM allocated (and I've increased max page size to 64k). I'm on EC2 (using ec2 discovery). Here are the entire contents of the logs: [http://streamified.com/StreamifiedESLogs.zip](http://streamified.com/StreamifiedESLogs.zip)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 2:33am UTC](https://discuss.elastic.co/t/mysterious-red-cluster-status-has-happened-4x-now/12226/2 "2017-07-06T02:33:25Z")

</div>