I want to upgrade my ES cluster(current version: 7.6.2) to the latest version (7.15.2 until now)
Is it ok to upgrade directly to the latest version or should I upgrade with 2 or 3 steps on different version?
For instance, for upgrading mongo db, it should be upgraded step by step to the next version...
I just want to know what is the policy or even best practice for upgrading ES ?!?
Thanks
It's totally fine to update between minor versions (7.x -> 7.y) as well as one major version up from latest minor version (6.8 -> 7.y), see upgrading document for the details. Best of all, it can be a rolling upgrade so you can upgrade nodes in the cluster one by one without cluster downtime or data loss. Just make sure cluster health is green before moving on to the next node.
Related
I want to upgrade spring framework from 4 to 5. Should i go with latest version such as 5.2.6 or any prior version i.e 5.2.0 or 5.2.4 etc? How should i decide on this ? I don't have any specific feature in mind.Thanks,
Don't see any reason not going for the latest.
Usually the major releases (from 4 to 5) might break something, so you might want to wait if it requires a lot of changes on your side, but if you're going to move to 5.2.x - go for the latest
SonarQube Community,
I upgraded from SonarQube 5.6 to 5.6.6 and the DB migration appeared to complete successfully.
Afterwards some of the projects summary data when drilling into the project does not show correctly while other projects do.
I have provide a link to the 3 items, two pngs showing visually what I am trying to communicate and the third with the log output from the upgrade and data migration.
I have rolled back to the old DB data as well as 5.6 and done this upgrade twice with the same outcome so it can be reproduced.
Is there something I need to know in doing this upgrade that I may have missed?
I have done several upgrades over the years and this is the first time I have seen this problem.
Thanks for any help you may be able to provide.
Doug
This is a case of a corrupted ElasticSearch index. It can be fixed by deleting _$SONARQUBE_HOME/data/es_.
From your comments, it looks like you carried over the ES index from your previous version. Instead, you should have
turned off your old version
exploded the zip for the new version
pointed the new version at your database
(re)installed your plugins
started the new version and allowed the ES indices to automatically (re)generate as part of the upgrade process
My projects java version runs on 1.7.0_71. and my elastic search version is 1.4.3 . Now we want to upgrade the es to 2.3.5. Is it ok to simply upgrade the elastic search version from 1.4.3 to 2.3.5. or should i upgrade the java to 1.8 then migrate it to 5.1 .. because my ultimate target is to for elastic search 5.1 version.
It should be ok to upgrade from 1.4 to 2.3, but it will be trickier (impossible) to go straight from 1.4 to 5.1 or 1.4->2.3->5.x without reindexing.
Segments created two Lucene major versions back are not supported.
So, even if you updgrade to 2.3, there still might be old segments (created in 1.4) when you upgrade to 5.x. There is an upgrade indices API, but as the documentation says it will not be useful for a 1.x -> 5.x upgrade.
Regarding the Java version, yes, you need Java 1.8, at least update 73: https://www.elastic.co/guide/en/elasticsearch/reference/5.1/setup.html#jvm-version
I am new in elasticsearch and I have by mistake installed 0.90.7 version in my server. Now I want to install shield for this I have to upgrade my elasticsearch version to 1.5 or above. So I need to Upgrade version without loosing existing data. Can anybody help me how to upgrade version to 1.6.1?
You can upgrade your Elasticsearch version from 0.90.x to 1.x in the following way
Cluster restart upgrade process
Before upgrading Elasticsearch, it is a good idea to consult the breaking changes docs.
As per Elasticsearch Documentation before performing an upgrade, it’s a good idea to back up the data on your system.
I am getting this error in one or two nodes in a Hadoop cluster, where rest of the nodes are running fine:
ERROR org.apache.hadoop.hdfs.server.datanode.DataNode: java.io.IOException:
*********** Upgrade is not supported from this older version of storage to
the current version. Please upgrade to Hadoop-0.14 or a later version and
then upgrade to current version. Old layout version is 'too old' and latest
layout version this software version can upgrade from is -7.
Any idea how to fix this problem, without losing the data?