# Restoring cluster with missing shards

**URL:** https://discuss.elastic.co/t/restoring-cluster-with-missing-shards/20756
**Category:** Elasticsearch
**Created:** [November 14, 2014, 5:15pm UTC](https://discuss.elastic.co/t/restoring-cluster-with-missing-shards/20756 "2014-11-14T17:15:32Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![mhughes](https://avatars.discourse-cdn.com/v4/letter/m/85e7bf/32.png) [@mhughes](https://discuss.elastic.co/u/mhughes)
#### Post date: [November 14, 2014, 5:15pm UTC](https://discuss.elastic.co/t/restoring-cluster-with-missing-shards/20756/1 "2014-11-14T17:15:32Z")

</div>

Two of my three nodes had catastrophic disk loss. Cluster was set up with  
1 replica, 5 shards per index. Obviously the remaining node does not have  
all shards for each index.

The system still responds to queries though it obviously has holes in the  
data.

If I do nothing, my cluster status is going to report red until these  
indices get deleted. Is there anyway around that? Or do I need to just  
bite the bullet and drop the unhealthy indices?

--  
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/6e2fda41-669f-4070-8f87-545bff9043e5%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/6e2fda41-669f-4070-8f87-545bff9043e5%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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, 12:49am UTC](https://discuss.elastic.co/t/restoring-cluster-with-missing-shards/20756/2 "2017-07-06T00:49:55Z")

</div>


