-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] upgrading opensearch cluster (eg. from 2.2.1 to 2.3.0) #95
Comments
Adding @rodolfovillordo can you add your thoughts here? |
Hey @erikrs do you continue to see this error? |
I just encountered the same tried to upgrade old install and I think the problem relates to #25 |
Hey @Kampfmoehre thanks, can you please contribute with the fix? |
I don't have a fix unfortunately. I opened the ticket one year ago when we wanted to replace Elastic Search with OpenSearch but we had difficulties with it. So we stick with ES until now where I try once again to make OS work. |
Hello. I got a similar problem when upgrading from 2.8.0 to 2.10.0. You can add a task to the beginning of main.yml:
|
Describe the bug
When upgrading opensearch, eg. from 2.2.1 to 2.3.0, opensearch fails to restart with a "jar hell" error
To Reproduce
a full (multi-node) opensearch installation was previously executed, eg os_version: "2.2.1"
Change all.yml: os_version: "2.3.0"
Run the playbook
See the error on the server:
Playbook Name Specify the Playbook which is affected?
Screenshots N/A
Host/Environment (please complete the following information):
Additional context
probably because the files from the new tar are extracted to existing os_home dir, and land next to older existing files, there's this "jar hell" problem ?
The text was updated successfully, but these errors were encountered: