# Upgrading Elasticsearch

**URL:** <https://discuss.elastic.co/t/upgrading-elasticsearch/289319>\
**Category:** Elasticsearch\
**Created:** [November 16, 2021, 12:00pm UTC](https://discuss.elastic.co/t/upgrading-elasticsearch/289319 "2021-11-16T12:00:39Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Farid\_N](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/farid_n/32/74144_2.png) [@Farid\_N](https://discuss.elastic.co/u/Farid_N)\
**Post date:** [November 16, 2021, 12:00pm UTC](https://discuss.elastic.co/t/upgrading-elasticsearch/289319/1 "2021-11-16T12:00:39Z")

</div>

Dear team,  
I want to upgrade my ES cluster to a newer version.  
This is the version I`m using:  
 ![image](https://us1.discourse-cdn.com/elastic/original/3X/0/9/097659f6e9a66ebcca07b204a6d8919c16730dac.png)

According to the bellow page:

> **[Rolling upgrades | Elasticsearch Guide \[7.15\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/rolling-upgrades.html)**

I just want to know can I upgrade my cluster with `Rolling Upgrade` ?

Or which way should I consider to upgrade my cluster and have the service up simultaneously...?  
I have a cluster with 4nodes of ES data and 1node of Kibana instance.

I've already checked this page:

> **[Migrating your Elasticsearch data | Elasticsearch Service Documentation |...](https://www.elastic.co/guide/en/cloud/current/ec-migrate-data.html)**

I need a vision of what should I do  
Thanks

---

<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:** [November 16, 2021, 10:05pm UTC](https://discuss.elastic.co/t/upgrading-elasticsearch/289319/2 "2021-11-16T22:05:28Z")

</div>

> [@Farid\_N](#):
>
> I just want to know can I upgrade my cluster with `Rolling Upgrade` ?

Yes that is the best way to do it.

---

<div class="post-metadata">

**Author:** ![Farid\_N](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/farid_n/32/74144_2.png) [@Farid\_N](https://discuss.elastic.co/u/Farid_N)\
**Post date:** [November 17, 2021, 10:19am UTC](https://discuss.elastic.co/t/upgrading-elasticsearch/289319/3 "2021-11-17T10:19:22Z")

</div>

Thanks alot

---

<div class="post-metadata">

**Author:** ![Farid\_N](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/farid_n/32/74144_2.png) [@Farid\_N](https://discuss.elastic.co/u/Farid_N)\
**Post date:** [November 24, 2021, 5:51am UTC](https://discuss.elastic.co/t/upgrading-elasticsearch/289319/4 "2021-11-24T05:51:15Z")

</div>

Just one another question:  
How can I run newer version on a node which older version is running?  
my Elasticsearch runs on a CentOS with SysV. I got the new version of Elasticsearch.tar and extracted it in `/home/my_user` directory and changed the `elasticsearch.yml` to older version's config specifics.  
Disabled shard allocation and also did "sync flush" then stopped older version:  
` service elasticsearch stop`  
Now I want to run the newer version with the same config file... What should I do?  
How can I run new Elasticsearch?  
This is `elasticsearch.yml` of my newer version: (same as the older one)

```auto
cluster.name: logServer
node.name: elk2
node.master: true
node.data: true
path.data: /var/lib/elasticsearch
path.logs: /var/log/elasticsearch
network.host: 0.0.0.0
transport.host: 172.22.34.37
http.port: 9200
discovery.zen.minimum_master_nodes: 1
discovery.zen.ping.unicast.hosts: ["172.22.34.36" , "172.22.34.37"]

```

---

<div class="post-metadata">

**Author:** ![Farid\_N](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/farid_n/32/74144_2.png) [@Farid\_N](https://discuss.elastic.co/u/Farid_N)\
**Post date:** [November 24, 2021, 6:00am UTC](https://discuss.elastic.co/t/upgrading-elasticsearch/289319/5 "2021-11-24T06:00:35Z")

</div>

I saw this section:

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/b/d/bd787ff4d1573ba2435222d9e3f7ad1af8c98cc0.png)  
Could you please explain me with some more details?  
Thank you

---

<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:** [November 24, 2021, 8:49pm UTC](https://discuss.elastic.co/t/upgrading-elasticsearch/289319/6 "2021-11-24T20:49:22Z")

</div>

You need to run the binary directly - [Install Elasticsearch from archive on Linux or MacOS | Elasticsearch Guide [7.15] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/7.15/targz.html#targz-running)

---

<div class="post-metadata">

**Author:** ![Farid\_N](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/farid_n/32/74144_2.png) [@Farid\_N](https://discuss.elastic.co/u/Farid_N)\
**Post date:** [November 27, 2021, 12:05pm UTC](https://discuss.elastic.co/t/upgrading-elasticsearch/289319/7 "2021-11-27T12:05:08Z")

</div>

Thank you so much  
And last thing, is it ok to upgrade ES 7.6.2 directly to 7.15.2 ?  
Or should I upgrade to the latest version with specific step?

---

<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:** [November 28, 2021, 1:34am UTC](https://discuss.elastic.co/t/upgrading-elasticsearch/289319/8 "2021-11-28T01:34:02Z")

</div>

> [@Farid\_N](#):
>
> e ES 7.6.2 directly to 7.15.2 ?

elasticsearch might not be a problem. but kibana config has change a bit. but it won't be too much hassle. just turn to log file of kibana and it will tell you why it failed.

---

<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:** [December 26, 2021, 1:34am UTC](https://discuss.elastic.co/t/upgrading-elasticsearch/289319/9 "2021-12-26T01:34:49Z")

</div>

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