# Upgrade from ES 2.3.4 to 2.4.0 causes performance problem and than downgrading back faces shard relocation problem

**URL:** <https://discuss.elastic.co/t/upgrade-from-es-2-3-4-to-2-4-0-causes-performance-problem-and-than-downgrading-back-faces-shard-relocation-problem/61232>\
**Category:** Elasticsearch\
**Created:** [September 22, 2016, 10:12am UTC](https://discuss.elastic.co/t/upgrade-from-es-2-3-4-to-2-4-0-causes-performance-problem-and-than-downgrading-back-faces-shard-relocation-problem/61232 "2016-09-22T10:12:28Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![szabolcs\_szentes](https://avatars.discourse-cdn.com/v4/letter/s/f05b48/32.png) [@szabolcs\_szentes](https://discuss.elastic.co/u/szabolcs_szentes)\
**Post date:** [September 22, 2016, 10:12am UTC](https://discuss.elastic.co/t/upgrade-from-es-2-3-4-to-2-4-0-causes-performance-problem-and-than-downgrading-back-faces-shard-relocation-problem/61232/1 "2016-09-22T10:12:28Z")

</div>

Hi,

After upgrading our ES cluster (3 nodes) from 2.3.4 to 2.4.0 the performance droped.  
The upgrade was a rolling upgrade with keeping the old confgiuration and data as well (no reindexing or restoring).

Than we decided to downgrade back to 2.3.4 but after downgrading one node and enabling shard allocation again it joins the cluster but it doesn not get any data (no shard is allocated to that node). Maybe because of Lucene version differences (2.3.4 has Lucene 5.5.0 and 2.4.0 has 5.5.2), just a guess.

Now we left with a cluster of 2 nodes (2.4.0) with reduced performance.  
We think about two options:

1. Try to reindex the data in this cluster to see if it would solve the performance problem - If it works than upgrade back the 3rd node again
2. Make a snapshot of the current data and set up a separate cluster of 2.3.4 nodes and try to restore the data there and see if the cluster is functional (shard allocation and performance wise)

This is the cluster health:  
{  
"cluster\_name" : "reco-cluster",  
"status" : "yellow",  
"timed\_out" : false,  
"number\_of\_nodes" : 3,  
"number\_of\_data\_nodes" : 3,  
"active\_primary\_shards" : 2,  
"active\_shards" : 4,  
"relocating\_shards" : 0,  
"initializing\_shards" : 0,  
"unassigned\_shards" : 2,  
"delayed\_unassigned\_shards" : 0,  
"number\_of\_pending\_tasks" : 0,  
"number\_of\_in\_flight\_fetch" : 0,  
"task\_max\_waiting\_in\_queue\_millis" : 0,  
"active\_shards\_percent\_as\_number" : 66.66666666666666  
}

Shards:  
reco-performers-1470150493712 0 p STARTED 798742 553.3mb 80.77.123.27 sonrisa2  
reco-performers-1470150493712 0 r STARTED 798742 553.3mb 80.77.123.28 sonrisa3  
reco-performers-1470150493712 0 r UNASSIGNED  
reco-performers-1470154237378 0 p STARTED 807498 854.4mb 80.77.123.27 sonrisa2  
reco-performers-1470154237378 0 r STARTED 807498 854.2mb 80.77.123.28 sonrisa3  
reco-performers-1470154237378 0 r UNASSIGNED

Any other suggestion would be appreciated!  
Thanks  
Szabolcs

---

<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 5, 2017, 10:18pm UTC](https://discuss.elastic.co/t/upgrade-from-es-2-3-4-to-2-4-0-causes-performance-problem-and-than-downgrading-back-faces-shard-relocation-problem/61232/2 "2017-07-05T22:18:08Z")

</div>

Closed on July 5, 2017, 10:18pm UTC