# ElasticSearch Version Upgrade and OS migration

**URL:** <https://discuss.elastic.co/t/elasticsearch-version-upgrade-and-os-migration/355820>\
**Category:** Elasticsearch\
**Created:** [March 20, 2024, 2:09pm UTC](https://discuss.elastic.co/t/elasticsearch-version-upgrade-and-os-migration/355820 "2024-03-20T14:09:15Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![mukularora89](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mukularora89/32/126696_2.png) [@mukularora89](https://discuss.elastic.co/u/mukularora89)\
**Post date:** [March 20, 2024, 2:09pm UTC](https://discuss.elastic.co/t/elasticsearch-version-upgrade-and-os-migration/355820/1 "2024-03-20T14:09:15Z")

</div>

Hi,

We have a requirement where we need to upgrade OS and for Elasticsearch to run properly on new OS we need to upgrade ES version too.

Here we have two options

Option 1 -

1. Upgrade Elasticsearch version on all nodes first
2. Perform OS migration on nodes with upgraded Elasticsearch version. For this we will take the node out of cluster and perform OS migration,install Elasticsearch upgraded version. Here cluster will have nodes with two different OS but with same Elasticsearch version.
3. Repeat step 2 for all the nodes

Option 2 -

1. Take node out, perform OS migration and install upgraded Elasticsearch version.
2. Put the node with new OS and upgraded Elasticsearch version into cluster. Here cluster will have nodes with two different OS and with different Elasticsearch version.
3. Repeat the step 1 and 2 for all the nodes

Do you see any problem with any options, particularly option 2? Thanks

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [March 20, 2024, 2:18pm UTC](https://discuss.elastic.co/t/elasticsearch-version-upgrade-and-os-migration/355820/2 "2024-03-20T14:18:04Z")

</div>

Between which Elasticsearch versions are you migrating? What is the size and topology of your cluster?

---

<div class="post-metadata">

**Author:** ![mukularora89](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mukularora89/32/126696_2.png) [@mukularora89](https://discuss.elastic.co/u/mukularora89)\
**Post date:** [March 20, 2024, 2:20pm UTC](https://discuss.elastic.co/t/elasticsearch-version-upgrade-and-os-migration/355820/3 "2024-03-20T14:20:53Z")

</div>

We are migrating Elasticsearch from 7.17.8 to 8.x most likely (8.12.2). We have around 50-60 data nodes, 3 master and 2 kibana nodes.

---

<div class="post-metadata">

**Author:** ![elasticforme](https://avatars.discourse-cdn.com/v4/letter/e/f05b48/32.png) [@elasticforme](https://discuss.elastic.co/u/elasticforme)\
**Post date:** [March 20, 2024, 9:43pm UTC](https://discuss.elastic.co/t/elasticsearch-version-upgrade-and-os-migration/355820/4 "2024-03-20T21:43:41Z")

</div>

I will prefer to have all elastic same version.

i.e option 1.  
you upgrading 7.x to 8.x. I hope you have already tested this out.

---

<div class="post-metadata">

**Author:** ![mukularora89](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mukularora89/32/126696_2.png) [@mukularora89](https://discuss.elastic.co/u/mukularora89)\
**Post date:** [March 21, 2024, 2:56pm UTC](https://discuss.elastic.co/t/elasticsearch-version-upgrade-and-os-migration/355820/5 "2024-03-21T14:56:28Z")

</div>

yes we are finalising the approaches then will test it out. So as of now comparing the different approaches.

---

<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:** [April 18, 2024, 2:56pm UTC](https://discuss.elastic.co/t/elasticsearch-version-upgrade-and-os-migration/355820/6 "2024-04-18T14:56:44Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
