# Unassigned shards after updating # of replica

**URL:** <https://discuss.elastic.co/t/unassigned-shards-after-updating-of-replica/19219>\
**Category:** Elasticsearch\
**Created:** [August 12, 2014, 6:53am UTC](https://discuss.elastic.co/t/unassigned-shards-after-updating-of-replica/19219 "2014-08-12T06:53:07Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Yaniv\_Yancovich](https://avatars.discourse-cdn.com/v4/letter/y/eb8c5e/32.png) [@Yaniv\_Yancovich](https://discuss.elastic.co/u/Yaniv_Yancovich)\
**Post date:** [August 12, 2014, 6:53am UTC](https://discuss.elastic.co/t/unassigned-shards-after-updating-of-replica/19219/1 "2014-08-12T06:53:07Z")

</div>

Hi,  
I am using ES 0.90.13 with 10 clusters. Java Sun 1.7.53.

We find out that the # of replicas on our ES clusters was zero.  
Hence, we increased the # of replica last week on ES2 to 1.  
Since then the cluster became yellow \<-\> green. It runs fine for several  
hours and then became yellow (with X unassigned shards). After few hours it  
became green.

Most of the time it became green, but from time few time it is stacked on 2  
unassigned shards.

From the logs:

[index.shard.service] [es2-s01] [ds77777][3] suspect illegal state: trying  
to move shard from primary mode to replica mode

[2014-08-11 00:33:10,384][WARN][cluster.action.shard] [es2-s02]  
[ds6765431\_1\_s][1] sending failed shard for [ds6765431\_1\_s][1],  
node[M34ta1aGTv-S4ahkrXK5DA], [R], s[STARTED], indexUUID  
[4T8zV8r7RUu8UkvQYsoz3w], reason [master  
[es2-s03][4rJC0nkVR1SgZhAcOK2MZw][inet[/10.1.112.3:9300]]{data\_center=ny4,  
max\_local\_storage\_nodes=1, master=true} marked shard as started, but shard  
has not been created, mark shard as failed]

This is a producation cluster. Please assist.  
Yaniv

--  
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/d2934403-9c04-42bd-9259-68313c25e1f6%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/d2934403-9c04-42bd-9259-68313c25e1f6%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, 1:09am UTC](https://discuss.elastic.co/t/unassigned-shards-after-updating-of-replica/19219/2 "2017-07-06T01:09:23Z")

</div>

Closed on July 6, 2017, 1:09am UTC


