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
Related
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.
I have installed and configured "1.7.2" version of elastic search. Now 2.0 version is released.
For time being, I want to have both directories (1.7.2 and 2.0) and want ES to use 2.0 version.
When I start ES, and access app, UI still shows 1.7.2 version. Basically auto discovery for newer version directory is not happening.
Can you please let me know how can I have ES point to 2.0 version directory. (I know 1 solution of running command and providing .yml path in parameter. Any other better solution)
/elasticsearch -fD es.config=/usr/local/es/elasticsearch/2.0/config/elasticsearch.yml
What version of NEST should i use for latest Elasticsearch version (2.1.1). We are planning to release our product in another 2 months and we are releasing with Elasticsearch 2.1.1 and wanted to know the right version of NEST to use
Nest has currently released version 2.0.0-alpha1 which should be compatible with Elasticsearch 2.x. I'm not sure when they will make Nest 2.0 generally available. You can download the pre-release version from here.
I'm looking to upgrade my Elasticsearch cluster to 1.4.5 or 1.5 and was curious if this upgrade will break my current codebase.
We are using NEST 1.3.1 in our code and I want to see if this version supports Elasticsearch 1.4.5 and higher? If you could link some documentation regarding this support, that would help me tremendously. Thank you all!
Did you consider upgrading Nest? Within the same major version, it is pretty much always backward compatible. With an older version of Nest and newer version of Elasticsearch, you would miss out on being able to use any new features that the newer version of Elasticsearch may provide. Anyways, you can read about the release notes of Nest here.
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.