-
Notifications
You must be signed in to change notification settings - Fork 273
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
[RELEASE] Release version 2.2.0 #2271
Comments
[Triaged] Release 2.2.0 issue, more details will be added after 2.1.0. |
Two new plugins will be added to 2.2 release. #2346 |
@opensearch-project/engineering-effectiveness there is no owner on this issue and the roadmap says the release is scheduled for the 11th - is there a new mechanism for tracking release processes or is this issue out of date? |
This is a release template for major, minor and patch releases. Feature freeze / code complete is targeted for August 4, 2022 with release date set to August 11, 2022 for 2.2 release. @peterzhuamazon please update the template with these dates. |
I have added the dates now @bbarani will add the individual issues soon. |
OSD 4048:
|
Performance results comparison between OpenSearch 2.1 vs 2.2 version
|
Thanks @kotwanikunal. Looks like Indexing (P100) is >10% high, Querying on ARM without security >20% . Also memory seems inconsistent (P90 is higher than P99), is that an error in our computation or I am misunderstanding it? Were there any runs for opensearch-min (I assume all of these tests are for the bundle) ? |
Is it possible those columns are transposed in the table? Those values look like they would swap cleanly and mirror the previous versions memory usage |
AD test run after merged changes.
|
All security dashboards tests are passing in this run. |
@peternied @saratvemulapalli The differences in memory consumption seem to be introduced in the results here.
The tests have been re-run to circumvent any flakiness between runs. |
@kotwanikunal thats interesting. I am worried we either made improvements in 2.1 and probably loosing them in 2.2 or as @peternied suggested we are misreporting the columns. |
Integ Test Result OSD 4049 Videos of test failures: Click to expand the test logs here
|
Performance Test re-run results - The previous arm64 without security seemed to be an outlier which was rectified by the re-run.
|
|
RPM YUM verification:
|
Hi, Thanks for the release. Seems that build-tools for 2.2.0 is missing though? |
Seems to me that all maven artifacts for 2.2.0 are missing, can't find them anywhere... |
The plugin artifacts are not available and thus the plugin install command fails as well. % ./bin/opensearch-plugin install opensearch-sql --verbose
-> Installing opensearch-sql
-> Failed installing opensearch-sql
-> Rolling back opensearch-sql
-> Rolled back opensearch-sql BTW, it would be useful to improve the |
@lukas-vlcek OpenSearch currently does not have support to install standalone plugins (outside of native plugins inherited from Elasticsearch) using plugin install command. You can view more details and the workaround in the below thread https://forum.opensearch.org/t/download-urls-for-plugins-not-listed-anywhere/8297/6?u=bbarani |
We are looking into the maven artifacts. Filed an issue with sonatype to get some information. |
Hey everyone, the artifacts are available on maven now. https://repo1.maven.org/maven2/org/opensearch/opensearch/2.2.0/ |
Release OpenSearch and OpenSearch Dashboards 2.2.0
I noticed that a manifest was automatically created in manifests/2.2.0. Please follow the following checklist to make a release.
How to use this issue
This Release Issue
This issue captures the state of the OpenSearch release, its assignee is responsible for driving the release. Please contact them or @mention them on this issue for help. There are linked issues on components of the release where individual components can be tracked. More details are included in the Maintainers Release owner section.
Release Steps
There are several steps to the release process, these steps are completed as the whole release and components that are behind present risk to the release. The release owner completes the tasks in this ticket, whereas component owners resolve tasks on their ticket in their repositories.
Steps have completion dates for coordinating efforts between the components of a release; components can start as soon as they are ready far in advance of a future release.
Component List
To aid in understanding the state of the release there is a table with status indicating each component state. This is updated based on the status of the component issues.
Preparation
__REPLACE_RELEASE-__
placeholders have actual dates.CI/CD (Feature Freeze) - 2022/07/26 - 2022/08/04
Campaigns
Code Complete - 2022/07/26 - 2022/08/04
Release testing - 2022/08/05 - 2022/08/09
Performance testing validation - 2022/08/08 - 2022/08/09
Release - 2022/08/10 - 2022/08/11
v2.2.0
in all projects have been resolved.Post Release
2.2.0
release.2.2.0
release.Components
Legend
Issue tracking (Updated 2022/08/05 21:31 PST)
Issues:
The text was updated successfully, but these errors were encountered: