# Upgrade Elasticsearch from 6.8.23 to 8.4.1

**URL:** https://discuss.elastic.co/t/upgrade-elasticsearch-from-6-8-23-to-8-4-1/314126
**Category:** Elasticsearch
**Tags:** language-clients
**Created:** [September 10, 2022, 9:34pm UTC](https://discuss.elastic.co/t/upgrade-elasticsearch-from-6-8-23-to-8-4-1/314126 "2022-09-10T21:34:40Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![Taby](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/taby/32/88015_2.png) [@Taby](https://discuss.elastic.co/u/Taby)
#### Post date: [September 10, 2022, 9:34pm UTC](https://discuss.elastic.co/t/upgrade-elasticsearch-from-6-8-23-to-8-4-1/314126/1 "2022-09-10T21:34:40Z")

</div>

Hi.

I've few questions regarding a possible upgrade of Elasticsearch from 6.8.23 to 8.4.1.

Our application is based on Java 8 build using SBT play framework, currently running and using Elasticsearch 6.8.23 on Mac, Redhat 7, Amazon Linux 2, with a one node cluster, and installed Elasticsearch using zip download. Application uses ReadOnlyRest plugin.

1: Is it possible to upgrade Elasticsearch from 6.8.23 to 8.4.1? Because, currently we're using [elasticsearch-rest-high-level-client:6.8.23](https://mvnrepository.com/artifact/org.elasticsearch.client/elasticsearch-rest-high-level-client/6.8.23) and I see until date only [alpha 2 version of elasticsearch-rest-high-level-client is available for 8.4.1](https://mvnrepository.com/artifact/org.elasticsearch.client/elasticsearch-rest-high-level-client/8.0.0-alpha2). We don't want to use alpha/rc version unless stable version is released.

2: I read [here](https://www.elastic.co/guide/en/elasticsearch/client/java-rest/current/java-rest-high-compatibility.html), that High Level REST Client is deprecated in 7.15.0. With this, do we have two options here, if we still want to upgrade from 6.8.23 to 8.4.1?  
a) Either migrate from High Level Rest Client (HLRC) to the new Java API Client as mentioned [here](https://www.elastic.co/guide/en/elasticsearch/client/java-api-client/current/migrate-hlrc.html)  
b) Enable the compatibility mode in High Level Client version 7.16 to communicate with Elasticsearch 8.x as mentioned [here](https://www.elastic.co/guide/en/elasticsearch/client/java-rest/current/java-rest-high-compatibility.html)

3: Above in 2a there might be a need to rewrite code? But for 2b there won't be any need to rewrite code? Please if anyone can confirm.

4: Will there be any performance degradation in 2b?

Thanks.

---

<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: [September 11, 2022, 12:38am UTC](https://discuss.elastic.co/t/upgrade-elasticsearch-from-6-8-23-to-8-4-1/314126/2 "2022-09-11T00:38:41Z")

</div>

you only have one node cluster.

create new one node cluster with version 8.4.1 and duplicate work. it will be faster then you upgrading 6.x to 8.x which has many changes along the line.

---

<div class="post-metadata">

### Author: ![Taby](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/taby/32/88015_2.png) [@Taby](https://discuss.elastic.co/u/Taby)
#### Post date: [September 11, 2022, 8:01pm UTC](https://discuss.elastic.co/t/upgrade-elasticsearch-from-6-8-23-to-8-4-1/314126/3 "2022-09-11T20:01:55Z")

</div>

> [@elasticforme](#):
>
> you only have one node cluster.
> 
> create new one node cluster with version 8.4.1 and duplicate work. it will be faster then you upgrading 6.x to 8.x which has many changes along the line.

Hi.  
Could you elaborate what is meant by "duplicate work"? I think in our case, we will go for "full cluster update" instead of "Rolling update". Could you please also share your opinion on point 2 and 3 of OP? I'm happy to give a try to install 8.4.1 and configure our application, but needs some clarification on point 2 & 3 specifically.

Thanks.

---

<div class="post-metadata">

### Author: ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)
#### Post date: [September 12, 2022, 1:40am UTC](https://discuss.elastic.co/t/upgrade-elasticsearch-from-6-8-23-to-8-4-1/314126/4 "2022-09-12T01:40:02Z")

</div>

> [@Taby](#):
>
> I think in our case, we will go for "full cluster update" instead of "Rolling update".

It is not possible to upgrade from 6.8 to 8.X, you would need first to upgrade to the last minor version of 7.17, check the upgrade assistant to see if there are any issues and then upgrade to the last 8.X version.

I do not use the Java API, but as you already saw, the Java High Level REST API is deprecated, you should migrate to the new JAVA API and you will probably need to change some things in your code.

I would say that the best approach in your case is to spin-up a completely new Elasticsearch cluster in version 8.4 and use it to test you code before migrate your production cluster.

---

<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: [September 12, 2022, 3:07pm UTC](https://discuss.elastic.co/t/upgrade-elasticsearch-from-6-8-23-to-8-4-1/314126/5 "2022-09-12T15:07:41Z")

</div>

What I mean is what exactly Leandro said.

best way to move on this case is to spin up new cluster, take snapshot of data and restore in new cluster. test out all that java api etc.. on new cluster and stop old cluster when new one in fully working.

---

<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: [October 10, 2022, 3:08pm UTC](https://discuss.elastic.co/t/upgrade-elasticsearch-from-6-8-23-to-8-4-1/314126/6 "2022-10-10T15:08:12Z")

</div>

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