# Index stuck in yellow unable to assign replica due to translog corruption

**URL:** <https://discuss.elastic.co/t/index-stuck-in-yellow-unable-to-assign-replica-due-to-translog-corruption/356556>\
**Category:** Elasticsearch\
**Created:** [April 1, 2024, 12:46pm UTC](https://discuss.elastic.co/t/index-stuck-in-yellow-unable-to-assign-replica-due-to-translog-corruption/356556 "2024-04-01T12:46:25Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [April 1, 2024, 5:07pm UTC](https://discuss.elastic.co/t/index-stuck-in-yellow-unable-to-assign-replica-due-to-translog-corruption/356556/4 "2024-04-01T17:07:02Z")

</div>

I see, hmm. I think you might have to set `number_of_replicas: 0` to clear up the corrupted replicas and then set it back to the correct number.

Also note that translog corruption indicates that your storage is buggy or otherwise not safe to use - one common cause is that your storage is incorrectly reordering `write()` and `fsync()` calls. I strongly recommend fixing this ASAP.

---

_[View the full topic](https://discuss.elastic.co/t/index-stuck-in-yellow-unable-to-assign-replica-due-to-translog-corruption/356556)._