# Problems with mixed version cluster during rolling upgrade?

**URL:** <https://discuss.elastic.co/t/problems-with-mixed-version-cluster-during-rolling-upgrade/56318>\
**Category:** Elasticsearch\
**Created:** [July 25, 2016, 4:56pm UTC](https://discuss.elastic.co/t/problems-with-mixed-version-cluster-during-rolling-upgrade/56318 "2016-07-25T16:56:43Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![jthoni](https://avatars.discourse-cdn.com/v4/letter/j/b9e5f3/32.png) [@jthoni](https://discuss.elastic.co/u/jthoni)\
**Post date:** [July 25, 2016, 4:56pm UTC](https://discuss.elastic.co/t/problems-with-mixed-version-cluster-during-rolling-upgrade/56318/1 "2016-07-25T16:56:43Z")

</div>

I have been confounded trying to upgrade my cluster from 2.0.0 to 2.3.2 (see [Node upgraded 2.0.0 to 2.3.2 can’t communicate with other nodes in cluster](https://discuss.elastic.co/t/node-upgraded-2-0-0-to-2-3-2-cant-communicate-with-other-nodes-in-cluster/55925)). I have given up trying to in-place upgrade. Instead, I am bringing new nodes up with 2.3.2, and then I will pull out the nodes with 2.0.0.

I brought a new 2.3.2 cluster on-line, and it seems to be working (as opposed to when I brought an upgraded node online and all started failing). I know that a new node will not allocate to a node with an older version. When I brought the 2.3.2 node on-line, shards started allocating to it. I am guessing this is a one-way allocation. Is this a risky situation to be in? I don't want to pull a 2.0.0 node out, or add another 2.3.2 node in, until I know that all is well.

Thanks,  
~john

---

<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:** [July 26, 2016, 10:39am UTC](https://discuss.elastic.co/t/problems-with-mixed-version-cluster-during-rolling-upgrade/56318/2 "2016-07-26T10:39:31Z")

</div>

> [@jthoni](#):
>
> Is this a risky situation to be in?

Only if you lose the 2.0 nodes.

---

<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:32pm UTC](https://discuss.elastic.co/t/problems-with-mixed-version-cluster-during-rolling-upgrade/56318/3 "2017-07-05T22:32:56Z")

</div>