Skip to content

Enabled default throttling for all tasks submitted to cluster manager #17711

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

Merged

Conversation

gargmanik13
Copy link
Contributor

@gargmanik13 gargmanik13 commented Mar 27, 2025

Description

Enabled default throttling for all tasks submitted to cluster manager.

  • Added default threshold values based on task type in ClusterManagerThrottlingDefaults class
  • If default threshold value for a task type is not present in ClusterManagerThrottlingDefaults, then we will use 50 as default threshold

Related Issues

Resolves #17685

Check List

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.

@github-actions github-actions bot added Cluster Manager enhancement Enhancement or improvement to existing feature or request v3.0.0 Issues and PRs related to version 3.0.0 labels Mar 27, 2025
@gargmanik13 gargmanik13 force-pushed the enable_default_throttling branch 2 times, most recently from e8571ca to 031e751 Compare March 27, 2025 14:05
Copy link
Contributor

❌ Gradle check result for 031e751:

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 7aa3bc8:

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 7aa3bc8: null

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?

@gargmanik13 gargmanik13 force-pushed the enable_default_throttling branch from 7aa3bc8 to f7ca2c0 Compare March 28, 2025 05:15
Copy link
Contributor

❕ Gradle check result for f7ca2c0: UNSTABLE

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 Mar 28, 2025

Codecov Report

Attention: Patch coverage is 97.91667% with 2 lines in your changes missing coverage. Please review.

Project coverage is 72.57%. Comparing base (54e02a7) to head (56d8ddb).
Report is 18 commits behind head on main.

Files with missing lines Patch % Lines
...h/cluster/service/ClusterManagerTaskThrottler.java 77.77% 1 Missing and 1 partial ⚠️
Additional details and impacted files
@@             Coverage Diff              @@
##               main   #17711      +/-   ##
============================================
+ Coverage     72.47%   72.57%   +0.09%     
- Complexity    67034    67137     +103     
============================================
  Files          5478     5473       -5     
  Lines        310132   310132              
  Branches      45087    45058      -29     
============================================
+ Hits         224775   225071     +296     
+ Misses        66960    66693     -267     
+ Partials      18397    18368      -29     

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

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@gargmanik13
Copy link
Contributor Author

❕ Gradle check result for f7ca2c0: UNSTABLE

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

Test Result (1 failure / -34)
org.opensearch.cluster.MinimumClusterManagerNodesIT.testThreeNodesNoClusterManagerBlock

Flaky Test - #14289

Copy link
Contributor

❌ Gradle check result for d085a1b: 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?

@gargmanik13
Copy link
Contributor Author

@gargmanik13
Copy link
Contributor Author

Thanks for the change, @gargmanik13

Since we are already changing in every file where we configured throttling, can we make those Throttling keys as enums?

Sure, i've updated Throttling Keys as enum.

@gargmanik13 gargmanik13 force-pushed the enable_default_throttling branch 2 times, most recently from 40ecee0 to 399ca2a Compare April 24, 2025 06:06
Copy link
Contributor

❌ Gradle check result for 399ca2a: 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?

@gargmanik13 gargmanik13 force-pushed the enable_default_throttling branch from 399ca2a to 0c601e8 Compare April 24, 2025 08:49
Copy link
Contributor

❌ Gradle check result for 0c601e8: 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?

Signed-off-by: Manik Garg <gargmanik1317@gmail.com>
@gargmanik13 gargmanik13 force-pushed the enable_default_throttling branch from 0c601e8 to 56d8ddb Compare April 24, 2025 09:20
Copy link
Contributor

✅ Gradle check result for 56d8ddb: SUCCESS

@shwetathareja shwetathareja merged commit 6ce0628 into opensearch-project:main Apr 25, 2025
31 of 32 checks passed
@github-project-automation github-project-automation bot moved this from 👀 In review to ✅ Done in Cluster Manager Project Board Apr 25, 2025
@opensearch-trigger-bot
Copy link
Contributor

The backport to 3.0 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-3.0 3.0
# Navigate to the new working tree
pushd ../.worktrees/OpenSearch/backport-3.0
# Create a new branch
git switch --create backport/backport-17711-to-3.0
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 6ce06282aa3d2bbffe26448fcac23d1b3113112b
# Push it to GitHub
git push --set-upstream origin backport/backport-17711-to-3.0
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/OpenSearch/backport-3.0

Then, create a pull request where the base branch is 3.0 and the compare/head branch is backport/backport-17711-to-3.0.

@gargmanik13 gargmanik13 deleted the enable_default_throttling branch April 28, 2025 06:31
gargmanik13 added a commit to gargmanik13/OpenSearch that referenced this pull request Apr 28, 2025
…opensearch-project#17711)

Signed-off-by: Manik Garg <gargmanik1317@gmail.com>
(cherry picked from commit 6ce0628)
gargmanik13 added a commit to gargmanik13/OpenSearch that referenced this pull request Apr 28, 2025
…opensearch-project#17711)

Signed-off-by: Manik Garg <gargmanik1317@gmail.com>
(cherry picked from commit 6ce0628)
gargmanik13 added a commit to gargmanik13/OpenSearch that referenced this pull request Apr 28, 2025
…opensearch-project#17711)

Signed-off-by: Manik Garg <gargmanik1317@gmail.com>
(cherry picked from commit 6ce0628)
shwetathareja pushed a commit that referenced this pull request Apr 28, 2025
…#17711) (#18094)

(cherry picked from commit 6ce0628)

Signed-off-by: Manik Garg <gargmanik1317@gmail.com>
prudhvigodithi pushed a commit to prudhvigodithi/OpenSearch that referenced this pull request May 6, 2025
…opensearch-project#17711) (opensearch-project#18094)

(cherry picked from commit 6ce0628)

Signed-off-by: Manik Garg <gargmanik1317@gmail.com>
Signed-off-by: Prudhvi Godithi <pgodithi@amazon.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport 3.0 backport-failed Cluster Manager enhancement Enhancement or improvement to existing feature or request v3.0.0 Issues and PRs related to version 3.0.0
Projects
Status: ✅ Done
Development

Successfully merging this pull request may close these issues.

[Feature Request] Enable default throttling with thresholds based on task type for Cluster Manager in 3.0
4 participants