# Elasticsearch upgrade from 1.1.1 to 1.3.7

**URL:** <https://discuss.elastic.co/t/elasticsearch-upgrade-from-1-1-1-to-1-3-7/21315>\
**Category:** Elasticsearch\
**Created:** [December 18, 2014, 2:13pm UTC](https://discuss.elastic.co/t/elasticsearch-upgrade-from-1-1-1-to-1-3-7/21315 "2014-12-18T14:13:57Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Phani\_Nadiminti](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/phani_nadiminti/32/45381_2.png) [@Phani\_Nadiminti](https://discuss.elastic.co/u/Phani_Nadiminti)\
**Post date:** [December 18, 2014, 2:13pm UTC](https://discuss.elastic.co/t/elasticsearch-upgrade-from-1-1-1-to-1-3-7/21315/1 "2014-12-18T14:13:57Z")

</div>

Hi All,

I upgraded elastic search from version 1.1.1 to 1.3.7.all things are  
working fine but when i checked status of my cluster it is showing "yellow"  
like following i waited for long time but shards not relocating.

{  
"cluster\_name": "elasticsearch",  
"status": "yellow",  
"timed\_out": false,  
"number\_of\_nodes": 2,  
"number\_of\_data\_nodes": 2,  
"active\_primary\_shards": 78,  
"active\_shards": 78,  
"relocating\_shards": 0,  
"initializing\_shards": 0,  
"unassigned\_shards": 72  
}

status of cluster.

```
   i have 2 nodes node1 and node2 both nodes upgraded to 1.3.7 but when 

```

i check in es HQ plugin shard balancing is showing on node1 only it is not  
showing the same index status on node2.

But while starting server the nodes has been joined to gether and slave  
node (node 2) detected master as node1. why i am not getting node2 working  
here please help me out to change the yellow status to green.

Thanks & Regards,

phani

--  
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/797bccc4-98c9-4f07-ad08-44befef55f07%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/797bccc4-98c9-4f07-ad08-44befef55f07%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [December 18, 2014, 3:27pm UTC](https://discuss.elastic.co/t/elasticsearch-upgrade-from-1-1-1-to-1-3-7/21315/2 "2014-12-18T15:27:22Z")

</div>

You can try dropping the replicas, wait for things to go green, then readd  
them.  
This has worked for a few people on IRC with similar issues.

On 18 December 2014 at 15:13, [phani.nadiminti@goktree.com](mailto:phani.nadiminti@goktree.com) wrote:

> Hi All,
> 
> I upgraded Elasticsearch from version 1.1.1 to 1.3.7.all things are  
> working fine but when i checked status of my cluster it is showing "yellow"  
> like following i waited for long time but shards not relocating.
> 
> {  
> "cluster\_name": "elasticsearch",  
> "status": "yellow",  
> "timed\_out": false,  
> "number\_of\_nodes": 2,  
> "number\_of\_data\_nodes": 2,  
> "active\_primary\_shards": 78,  
> "active\_shards": 78,  
> "relocating\_shards": 0,  
> "initializing\_shards": 0,  
> "unassigned\_shards": 72  
> }
> 
> status of cluster.
> 
> ```
> i have 2 nodes node1 and node2 both nodes upgraded to 1.3.7 but
> 
> ```
> 
> when i check in es HQ plugin shard balancing is showing on node1 only it is  
> not showing the same index status on node2.
> 
> But while starting server the nodes has been joined to gether and slave  
> node (node 2) detected master as node1. why i am not getting node2 working  
> here please help me out to change the yellow status to green.
> 
> Thanks & Regards,
> 
> phani
> 
> --  
> 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/797bccc4-98c9-4f07-ad08-44befef55f07%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/797bccc4-98c9-4f07-ad08-44befef55f07%40googlegroups.com)  
> [https://groups.google.com/d/msgid/elasticsearch/797bccc4-98c9-4f07-ad08-44befef55f07%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/797bccc4-98c9-4f07-ad08-44befef55f07%40googlegroups.com?utm_medium=email&utm_source=footer)  
> .  
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
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/CAEYi1X9Ez5fm8sO538WzR7hfBNY6M%2BWyMJsvtv4v56xpFef9vA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X9Ez5fm8sO538WzR7hfBNY6M%2BWyMJsvtv4v56xpFef9vA%40mail.gmail.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:42am UTC](https://discuss.elastic.co/t/elasticsearch-upgrade-from-1-1-1-to-1-3-7/21315/3 "2017-07-06T00:42:50Z")

</div>