# Can't do rolling upgrade from 7.6.2 to 7.10.0

**URL:** <https://discuss.elastic.co/t/cant-do-rolling-upgrade-from-7-6-2-to-7-10-0/257549>\
**Category:** Elasticsearch\
**Created:** [December 3, 2020, 4:31pm UTC](https://discuss.elastic.co/t/cant-do-rolling-upgrade-from-7-6-2-to-7-10-0/257549 "2020-12-03T16:31:20Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![rambling](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rambling/32/79737_2.png) [@rambling](https://discuss.elastic.co/u/rambling)\
**Post date:** [December 3, 2020, 4:31pm UTC](https://discuss.elastic.co/t/cant-do-rolling-upgrade-from-7-6-2-to-7-10-0/257549/1 "2020-12-03T16:31:20Z")

</div>

Hello. I was trying to do rolling update data node from 7.6.2 to 7.10.0 on Ubuntu 18.04.  
I followed the instructions:

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

  
but after the update Elasticsearch can't start with next outputs:

```auto
Dec 03 17:15:21 test-es-data-05 systemd-entrypoint[1221]: Error: Could not create the Java Virtual Machine.
Dec 03 17:15:21 test-es-data-05 systemd-entrypoint[1221]: Error: A fatal exception has occurred. Program will exit.
Dec 03 17:15:21 test-es-data-05 systemd-entrypoint[1221]: at org.elasticsearch.tools.launchers.JvmErgonomics.flagsFinal(JvmErgonomics.java:126)
Dec 03 17:15:21 test-es-data-05 systemd-entrypoint[1221]: at org.elasticsearch.tools.launchers.JvmErgonomics.finalJvmOptions(JvmErgonomics.java:88)
Dec 03 17:15:21 test-es-data-05 systemd-entrypoint[1221]: at org.elasticsearch.tools.launchers.JvmErgonomics.choose(JvmErgonomics.java:59)
Dec 03 17:15:21 test-es-data-05 systemd-entrypoint[1221]: at org.elasticsearch.tools.launchers.JvmOptionsParser.jvmOptions(JvmOptionsParser.java:137)
Dec 03 17:15:21 test-es-data-05 systemd-entrypoint[1221]: at org.elasticsearch.tools.launchers.JvmOptionsParser.main(JvmOptionsParser.java:95)
Dec 03 17:15:21 test-es-data-05 systemd[1]: elasticsearch.service: Main process exited, code=exited, status=1/FAILURE
Dec 03 17:15:21 test-es-data-05 systemd[1]: elasticsearch.service: Failed with result 'exit-code'.
Dec 03 17:15:21 test-es-data-05 systemd[1]: Failed to start Elasticsearch.

```

after updating Elasticsearch I also updated `jvm.options` based on clear 7.10.0 version, here:

```auto
-Xms16069m
-Xmx16069m
8-13:-XX:+UseConcMarkSweepGC
8-13:-XX:CMSInitiatingOccupancyFraction=75
8-13:-XX:+UseCMSInitiatingOccupancyOnly
14-:-XX:+UseG1GC
14-:-XX:G1ReservePercent=25
14-:-XX:InitiatingHeapOccupancyPercent=30
-Djava.io.tmpdir=${ES_TMPDIR}
-XX:+HeapDumpOnOutOfMemoryError
-XX:HeapDumpPath=/var/lib/elasticsearch
-XX:ErrorFile=/var/log/elasticsearch/hs_err_pid%p.log
8:-XX:+PrintGCDetails
8:-XX:+PrintGCDateStamps
8:-XX:+PrintTenuringDistribution
8:-XX:+PrintGCApplicationStoppedTime
8:-Xloggc:/var/log/elasticsearch/gc.log
8:-XX:+UseGCLogFileRotation
8:-XX:NumberOfGCLogFiles=32
8:-XX:GCLogFileSize=64m
9-:-Xlog:gc*,gc+age=trace,safepoint:file=/var/log/elasticsearch/gc.log:utctime,pid,tags:filecount=32,filesize=64m 

```

JDK updated succesfully:

```auto
/usr/share/elasticsearch/jdk/bin/java -version
openjdk version "15.0.1" 2020-10-20
OpenJDK Runtime Environment AdoptOpenJDK (build 15.0.1+9)
OpenJDK 64-Bit Server VM AdoptOpenJDK (build 15.0.1+9, mixed mode, sharing)

```

So, how can i debug this issue or to which version should I update?

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [December 3, 2020, 4:57pm UTC](https://discuss.elastic.co/t/cant-do-rolling-upgrade-from-7-6-2-to-7-10-0/257549/2 "2020-12-03T16:57:32Z")

</div>

The answer will be in the Elasticsearch server logs. The `systemd` ones only show the last couple of lines of the error which isn't enough.

Also in 7.10 you should leave the `jvm.options` file untouched and use [separate options files](https://www.elastic.co/guide/en/elasticsearch/reference/current/jvm-options.html) for any customisation.

---

<div class="post-metadata">

**Author:** ![rambling](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rambling/32/79737_2.png) [@rambling](https://discuss.elastic.co/u/rambling)\
**Post date:** [December 4, 2020, 7:07am UTC](https://discuss.elastic.co/t/cant-do-rolling-upgrade-from-7-6-2-to-7-10-0/257549/3 "2020-12-04T07:07:43Z")

</div>

> [@DavidTurner](#):
>
> Also in 7.10 you should leave the `jvm.options` file untouched

The `jvm.options` file which I provided in previous post is mostly untouched except all comments and this lines:

```auto
-Xms16069m
-Xmx16069m

```

Anyway I just used `jvm.options` from fresh 7.10.0 install and then override `-Xms/x` in `/etc/elasticsearch/jvm.options.d/jvm.config` and Elasticsearch start on new version.  
Thanks for help!

---

<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:** [January 1, 2021, 7:07am UTC](https://discuss.elastic.co/t/cant-do-rolling-upgrade-from-7-6-2-to-7-10-0/257549/4 "2021-01-01T07:07:54Z")

</div>

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