Hello
I have a running cluster with 3 nodes, latest 2.19 version.
is it possible to upgrade to version 3.1 without interrupting the service?
I find that the documentation isn’t very clear for major upgrade.
My cluster is runnng on Ubuntu 22.04 with 2.x repo.
Thanks
Yathus
I would also like to know how to do this.
@Yathus @danrk OS3.1 supports running versions as low as 2.19.0, therefore it is possible to perform a rolling upgrade by following the typical steps outlined in the docs
I have just tested using tarballs for 2.19.0 and 3.1.0 and the steps worked.
There are some changes in the jvm.options that you should be aware of (mentioned in this post) prior to upgrading this in production, to ensure no downtime.
As always the recommendation is to try this in dev/test first.
I’m part of the OpenSearch Migration’s team, we’ve got tooling that can be used to migrate even self-managed clusters for a variety of scenarios. By default its deploy and orchestrated on an AWS account and we have a kubernetes deployment in flight under /deployment/k8/... within the project repo for cloud-less migrations GitHub - opensearch-project/opensearch-migrations: Migrate, upgrade, compare, and replicate OpenSearch clusters with ease.
Our public documentation - Migration Assistant for OpenSearch - OpenSearch Documentation