-
Notifications
You must be signed in to change notification settings - Fork 61
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
Plugin upgrade path from versions prior to OpenSearch 1.0.0 #39
Comments
We did mixed cluster test Elasticsearch 7.x and OpenSearch 1.x without any plugins. The OpenSearch node doesn’t join the cluster due to an open issue: opensearch-project/OpenSearch#669 |
Related issue after this is taken care of is: opensearch-project/opensearch-build#42 |
I have tested manually using these steps: Restart Upgrade:
Rolling Upgrade:
|
I think we should close this, the feature is implemented across the board, @saratvemulapalli ? |
Agreed. I'll open a new one for automated tests. |
Reopening this as indexing during rolling upgrades is not supported and potentially will impact Alerting, AD etc |
Did the above test is with security enabled? |
No this was without security plugin. Infact all the plugins were purged and installed Job-Scheduler, AD. |
Closing this as the fix in security is merged. |
As part of getting the plugins ready for backwards compatibility the last of the items on #12 are:
As 1 and 2 are very similar, to break down the problem we'll focus on 1.
We see 2 different upgrade paths:
In order to perform and verify this backwards compatibility during upgrades plugins need to have a way to test these scenarios.
Ref: OpenSearch does this today with Bwc tests. Eg: https://github.com/opensearch-project/OpenSearch/blob/main/qa/mixed-cluster/build.gradle
The text was updated successfully, but these errors were encountered: