# Unassigned Replica Shards - Sync Id Match

**URL:** <https://discuss.elastic.co/t/unassigned-replica-shards-sync-id-match/74724>\
**Category:** Elasticsearch\
**Created:** [February 10, 2017, 11:04pm UTC](https://discuss.elastic.co/t/unassigned-replica-shards-sync-id-match/74724 "2017-02-10T23:04:12Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Russell\_Day](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/russell_day/32/30779_2.png) [@Russell\_Day](https://discuss.elastic.co/u/Russell_Day)\
**Post date:** [February 10, 2017, 11:04pm UTC](https://discuss.elastic.co/t/unassigned-replica-shards-sync-id-match/74724/1 "2017-02-10T23:04:12Z")

</div>

I encountered an issue this week where my cluster went yellow and I had a large number of unassigned replicas. Relocate worked only for a very small number of the shards. Allocation/explain returned the message below. I tried setting the index from 1 replica to 0 replica then back to 1 to try to re-initialize the replica but it did not resolve the issue. It seemed like the replica shards were orphaned in some manner. Any feedback for what might have caused this and how to resolve would be great. Running v 5.1.1 on AWS.

"details" : "existing allocation of replica to [{nodeNameRemoved}{ODEM6\_OxSmmlCaVfir-Tmw}{w1b-HhGPQgi47Zfri7h7LA}{removed:8193}{availability\_zone=us-east-1b, instance\_type=removed, external\_ip=removed, tags=Data}] cancelled, sync id match found on node [{nodeNameRemoved}...

---

<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:** [March 10, 2017, 11:04pm UTC](https://discuss.elastic.co/t/unassigned-replica-shards-sync-id-match/74724/2 "2017-03-10T23:04:30Z")

</div>

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