# Shards go unassigned and recovery mode

**URL:** <https://discuss.elastic.co/t/shards-go-unassigned-and-recovery-mode/188736>\
**Category:** Elasticsearch\
**Created:** [July 3, 2019, 2:14pm UTC](https://discuss.elastic.co/t/shards-go-unassigned-and-recovery-mode/188736 "2019-07-03T14:14:15Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![zatom](https://avatars.discourse-cdn.com/v4/letter/z/f0a364/32.png) [@zatom](https://discuss.elastic.co/u/zatom)\
**Post date:** [July 3, 2019, 2:14pm UTC](https://discuss.elastic.co/t/shards-go-unassigned-and-recovery-mode/188736/1 "2019-07-03T14:14:15Z")

</div>

Hi,

Lately one of my huge reindexing failed in the middle. It stopped after reindexing 1.5TB. Since then, when you try to reindex everytime, some shards gets unassigned and some goes on recovery mode, Cluster health goes RED. And it takes all day to recover all the shards back.

How do I avoid such things in future?

---

<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 31, 2019, 2:14pm UTC](https://discuss.elastic.co/t/shards-go-unassigned-and-recovery-mode/188736/2 "2019-07-31T14:14:15Z")

</div>

Closed on July 31, 2019, 2:14pm UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.