# Upgrade the Elasticsearch to 7.10 version warning

**URL:** <https://discuss.elastic.co/t/upgrade-the-elasticsearch-to-7-10-version-warning/269756>\
**Category:** Elasticsearch\
**Created:** [April 10, 2021, 3:15am UTC](https://discuss.elastic.co/t/upgrade-the-elasticsearch-to-7-10-version-warning/269756 "2021-04-10T03:15:42Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![loxiaopohaiol](https://avatars.discourse-cdn.com/v4/letter/l/d78d45/32.png) [@loxiaopohaiol](https://discuss.elastic.co/u/loxiaopohaiol)\
**Post date:** [April 10, 2021, 3:15am UTC](https://discuss.elastic.co/t/upgrade-the-elasticsearch-to-7-10-version-warning/269756/1 "2021-04-10T03:15:42Z")

</div>

I have a elasticsearch cluster about 6 node(3 masters , 3 data,the version is 6.6, running through the docker), and then, I want to upgrade it from 6.6 to 7.10 , accronding to the Official document ， I must upgrade my cluster to 6.8 first , and then upgrade to 7.10. I did these steps, and final the cluster upgrade is ok , but I found that have some warning logs in the version 7.10:  
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".  
SLF4J: Defaulting to no-operation (NOP) logger implementation.  
SLF4J: See [SLF4J Error Codes](http://www.slf4j.org/codes.html#StaticLoggerBinder) for further details.

I think it maybe impact my cluster‘s status logs, because I test that: I stop a node elasitcsearch , and the master's log just out put the log for shard, no log to the node for leave the cluster ,and then the stopped elasticsearch node is starting , there is also no logs for the node join into the cluster in the master node logs. Is that normal for the cluster?

how can I fix this issue?

---

<div class="post-metadata">

**Author:** ![loxiaopohaiol](https://avatars.discourse-cdn.com/v4/letter/l/d78d45/32.png) [@loxiaopohaiol](https://discuss.elastic.co/u/loxiaopohaiol)\
**Post date:** [April 10, 2021, 4:21am UTC](https://discuss.elastic.co/t/upgrade-the-elasticsearch-to-7-10-version-warning/269756/2 "2021-04-10T04:21:58Z")

</div>

I have another test, when I upgrade the 6.6 to 6.8, the elasticsearch node has also have this warning.

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [April 10, 2021, 6:34am UTC](https://discuss.elastic.co/t/upgrade-the-elasticsearch-to-7-10-version-warning/269756/3 "2021-04-10T06:34:33Z")

</div>

What kind of upgrade did you try?  
What exact steps did you run?

---

<div class="post-metadata">

**Author:** ![loxiaopohaiol](https://avatars.discourse-cdn.com/v4/letter/l/d78d45/32.png) [@loxiaopohaiol](https://discuss.elastic.co/u/loxiaopohaiol)\
**Post date:** [April 10, 2021, 6:48am UTC](https://discuss.elastic.co/t/upgrade-the-elasticsearch-to-7-10-version-warning/269756/4 "2021-04-10T06:48:26Z")

</div>

I use the rolling upgrade node one by one. Before I upgrade the cluster, I just setting the cluster:  
PUT \_cluster/settings  
{  
"persistent": {  
"cluster": {  
"routing": {  
"allocation.enable": "none"  
}  
}  
}  
}

And then change the docker images from 6.6 to 6.8

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [April 10, 2021, 7:06am UTC](https://discuss.elastic.co/t/upgrade-the-elasticsearch-to-7-10-version-warning/269756/5 "2021-04-10T07:06:35Z")

</div>

How do you run the instance exactly?

Please format your code, logs or configuration files using `</>` icon as explained in [this guide](https://discuss.elastic.co/t/about-the-elasticsearch-category/21) and not the citation button. It will make your post more readable.

Or use markdown style like:

````
```
CODE
```

````

This is the icon to use if you are not using markdown format:

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/7/e/7e6e239431ec2d71cbf1beef741f2e93e7cc762c.jpg)

There's a live preview panel for exactly this reasons.

Lots of people read these forums, and many of them will simply skip over a post that is difficult to read, because it's just too large an investment of their time to try and follow a wall of badly formatted text.  
If your goal is to get an answer to your questions, it's in your interest to make it as easy to read and understand as possible.

---

<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:** [May 8, 2021, 7:07am UTC](https://discuss.elastic.co/t/upgrade-the-elasticsearch-to-7-10-version-warning/269756/6 "2021-05-08T07:07:12Z")

</div>

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