Skip to content
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

Prevent version upgrade during MIXED compatibility mode #13185

Merged
merged 2 commits into from
Apr 23, 2024

Conversation

ltaragi
Copy link
Contributor

@ltaragi ltaragi commented Apr 15, 2024

Description

  • During migration, primary shards always move first, while during version changes, replica shards move first.
  • Thus, in MIXED compatibility mode, as new nodes join the cluster, nodes with a higher version should not be allowed to join.
  • A check has been added in JoinTaskExecutor.java, where the compatibility of the joining node with the cluster is verified inside ensureRemoteStoreNodesCompatibility.

Related Issues

Resolves #13250

Check List

  • New functionality includes testing.
    • All tests pass
  • New functionality has been documented.
    • New functionality has javadoc added
  • Failing checks are inspected and point to the corresponding known issue(s) (See: Troubleshooting Failing Builds)
  • Commits are signed per the DCO using --signoff
  • Commit changes are listed out in CHANGELOG.md file (See: Changelog)
  • Public documentation issue/PR created

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Copy link
Contributor

github-actions bot commented Apr 15, 2024

Compatibility status:

Checks if related components are compatible with change 6723944

Incompatible components

Skipped components

Compatible components

Compatible components: [https://github.com/opensearch-project/custom-codecs.git, https://github.com/opensearch-project/asynchronous-search.git, https://github.com/opensearch-project/neural-search.git, https://github.com/opensearch-project/flow-framework.git, https://github.com/opensearch-project/job-scheduler.git, https://github.com/opensearch-project/cross-cluster-replication.git, https://github.com/opensearch-project/reporting.git, https://github.com/opensearch-project/security-analytics.git, https://github.com/opensearch-project/geospatial.git, https://github.com/opensearch-project/opensearch-oci-object-storage.git, https://github.com/opensearch-project/notifications.git, https://github.com/opensearch-project/common-utils.git, https://github.com/opensearch-project/k-nn.git, https://github.com/opensearch-project/observability.git, https://github.com/opensearch-project/anomaly-detection.git, https://github.com/opensearch-project/performance-analyzer-rca.git, https://github.com/opensearch-project/ml-commons.git, https://github.com/opensearch-project/index-management.git, https://github.com/opensearch-project/alerting.git, https://github.com/opensearch-project/security.git, https://github.com/opensearch-project/sql.git, https://github.com/opensearch-project/performance-analyzer.git]

Copy link
Contributor

❌ Gradle check result for 881eb9e: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

@ltaragi ltaragi changed the title Don't allow version upgrade during MIXED compatibility mode Prevent version upgrade during MIXED compatibility mode Apr 16, 2024
Copy link
Contributor

❕ Gradle check result for 6723944: UNSTABLE

  • TEST FAILURES:
      1 org.opensearch.cluster.coordination.AwarenessAttributeDecommissionIT.testConcurrentDecommissionAction

Please review all flaky tests that succeeded after retry and create an issue if one does not already exist to track the flaky failure.

Copy link

codecov bot commented Apr 16, 2024

Codecov Report

Attention: Patch coverage is 88.88889% with 1 lines in your changes are missing coverage. Please review.

Project coverage is 71.51%. Comparing base (b15cb0c) to head (686d1fe).
Report is 199 commits behind head on main.

Files Patch % Lines
...nsearch/cluster/coordination/JoinTaskExecutor.java 88.88% 0 Missing and 1 partial ⚠️
Additional details and impacted files
@@             Coverage Diff              @@
##               main   #13185      +/-   ##
============================================
+ Coverage     71.42%   71.51%   +0.09%     
- Complexity    59978    60708     +730     
============================================
  Files          4985     5039      +54     
  Lines        282275   285441    +3166     
  Branches      40946    41339     +393     
============================================
+ Hits         201603   204135    +2532     
- Misses        63999    64417     +418     
- Partials      16673    16889     +216     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@github-actions github-actions bot added enhancement Enhancement or improvement to existing feature or request Storage:Durability Issues and PRs related to the durability framework Storage:Remote labels Apr 17, 2024
Copy link
Contributor

✅ Gradle check result for 4b0d9ce: SUCCESS

Copy link
Contributor

❌ Gradle check result for 23bd998: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

Copy link
Contributor

❕ Gradle check result for b4305f6: UNSTABLE

  • TEST FAILURES:
      2 org.opensearch.cluster.allocation.ClusterRerouteIT.testDelayWithALargeAmountOfShards

Please review all flaky tests that succeeded after retry and create an issue if one does not already exist to track the flaky failure.

@astute-decipher
Copy link
Contributor

Overall LGTM, left a minor comment.

Copy link
Contributor

✅ Gradle check result for 686d1fe: SUCCESS

@dblock dblock requested a review from Bukhtawar April 22, 2024 13:16
@ltaragi ltaragi self-assigned this Apr 23, 2024
@gbbafna gbbafna merged commit 2aad499 into opensearch-project:main Apr 23, 2024
30 checks passed
@gbbafna gbbafna added the backport 2.x Backport to 2.x branch label Apr 23, 2024
@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.x failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/OpenSearch/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/OpenSearch/backport-2.x
# Create a new branch
git switch --create backport/backport-13185-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 2aad4998af0b20b28fd7dba009fdba4658bb130e
# Push it to GitHub
git push --set-upstream origin backport/backport-13185-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/OpenSearch/backport-2.x

Then, create a pull request where the base branch is 2.x and the compare/head branch is backport/backport-13185-to-2.x.

ltaragi added a commit to ltaragi/OpenSearch that referenced this pull request Apr 23, 2024
ltaragi added a commit to ltaragi/OpenSearch that referenced this pull request Apr 23, 2024
ltaragi added a commit to ltaragi/OpenSearch that referenced this pull request Apr 23, 2024
dblock pushed a commit that referenced this pull request Apr 23, 2024
Signed-off-by: Lakshya Taragi <[email protected]>
(cherry picked from commit 2aad499)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport 2.x Backport to 2.x branch backport-failed enhancement Enhancement or improvement to existing feature or request skip-changelog Storage:Durability Issues and PRs related to the durability framework Storage:Remote
Projects
Status: ✅ Done
Development

Successfully merging this pull request may close these issues.

[Remote Store] Prevent version upgrade during MIXED compatibility mode
4 participants