# Upgrade order (best practices)

**URL:** <https://discuss.elastic.co/t/upgrade-order-best-practices/26992>\
**Category:** Elasticsearch\
**Created:** [August 6, 2015, 4:50pm UTC](https://discuss.elastic.co/t/upgrade-order-best-practices/26992 "2015-08-06T16:50:56Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![podollb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/podollb/32/3703_2.png) [@podollb](https://discuss.elastic.co/u/podollb)\
**Post date:** [August 6, 2015, 4:50pm UTC](https://discuss.elastic.co/t/upgrade-order-best-practices/26992/1 "2015-08-06T16:50:56Z")

</div>

When upgrading a service (i.e. such as a spring boot application that uses the elasticsearch client library), and also an ElasticSearch cluster, to use a new version (say an upgrade from 1.6.0 to 1.6.2), what order is best practices?

I assume upgrading the service first, so it can startup using the newer elasticsearch client library 1.6.2 against an older ES cluster running 1.6.0, and then after that upgrade the cluster. I only assume that since the client library is likely backward compatible.

---

<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:** [August 7, 2015, 7:59am UTC](https://discuss.elastic.co/t/upgrade-order-best-practices/26992/2 "2015-08-07T07:59:32Z")

</div>

With such a small step you shouldn't really have to worry either way.

---

<div class="post-metadata">

**Author:** ![podollb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/podollb/32/3703_2.png) [@podollb](https://discuss.elastic.co/u/podollb)\
**Post date:** [August 7, 2015, 1:14pm UTC](https://discuss.elastic.co/t/upgrade-order-best-practices/26992/3 "2015-08-07T13:14:11Z")

</div>

Those were just example versions. I was more curious about best practices? So, in a more extreme case, if I was going from 1.4.2 to 1.7.1 what would be recommended (although I'd likely never get that outdated).

---

<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:** [August 7, 2015, 11:21pm UTC](https://discuss.elastic.co/t/upgrade-order-best-practices/26992/4 "2015-08-07T23:21:19Z")

</div>

It'd probably be better to upgrade ES and then the client.

But caveat; Larger versions are trickier and you really want to go over the change notes and readmes to make sure this will work.

---

<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, 11:56pm UTC](https://discuss.elastic.co/t/upgrade-order-best-practices/26992/5 "2017-07-05T23:56:46Z")

</div>


