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

Fixed primary shard balance constraints getting unset #15996

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

patelsmit32123
Copy link

@patelsmit32123 patelsmit32123 commented Sep 19, 2024

Description

Fixed updating shard balance factor and other such settings were unsetting the prefer primary shard balance constraints.

Related Issues

#13429

Check List

  • Functionality includes testing.
  • API changes companion pull request created, if applicable.
  • Public documentation issue/PR created, if applicable.

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.

@patelsmit32123
Copy link
Author

@peternied Can you please review?

Copy link
Contributor

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

@patelsmit32123 patelsmit32123 force-pushed the fix-shard-balance-constraints-unset branch from 360fbfa to f161334 Compare September 19, 2024 12:45
Copy link
Contributor

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

@patelsmit32123 patelsmit32123 force-pushed the fix-shard-balance-constraints-unset branch from f161334 to ca907c7 Compare September 19, 2024 13:16
Copy link
Contributor

❕ Gradle check result for ca907c7: 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 Sep 19, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 71.99%. Comparing base (3937ccb) to head (ca907c7).
Report is 231 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff              @@
##               main   #15996      +/-   ##
============================================
+ Coverage     71.90%   71.99%   +0.08%     
- Complexity    64392    64393       +1     
============================================
  Files          5278     5280       +2     
  Lines        300877   300875       -2     
  Branches      43478    43477       -1     
============================================
+ Hits         216351   216619     +268     
+ Misses        66747    66474     -273     
- Partials      17779    17782       +3     

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


🚨 Try these New Features:

@peternied
Copy link
Member

@patelsmit32123 Thanks for making this change and reaching out.

@gbbafna @Bukhtawar @ashking94 Could one of you review this PR in my place?

@ashking94
Copy link
Member

@patelsmit32123 Thanks for making this change and reaching out.

@gbbafna @Bukhtawar @ashking94 Could one of you review this PR in my place?

Hi @peternied, I will review this. Thanks @patelsmit32123 for making this change. Allow me some time to go over this.

Copy link
Member

@ashking94 ashking94 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we add a test (unit test or ITs) that covers the scenario mentioned in the issue #13429? The changes seem fine otherwise.

@patelsmit32123
Copy link
Author

@ashking94 how to test the scenario? The problem is that the allocation constraints which are getting unset, they are not accessible from outside.

@ashking94
Copy link
Member

@ashking94 how to test the scenario? The problem is that the allocation constraints which are getting unset, they are not accessible from outside.

Can we add some unit tests to ascertain that the behaviour works as expected? I see BalancedSingleShardTests where you can attempt to put the test against the delta. Let me know if this does not work.

@opensearch-trigger-bot
Copy link
Contributor

This PR is stalled because it has been open for 30 days with no activity.

@opensearch-trigger-bot opensearch-trigger-bot bot added stalled Issues that have stalled and removed stalled Issues that have stalled labels Oct 24, 2024
@opensearch-trigger-bot
Copy link
Contributor

This PR is stalled because it has been open for 30 days with no activity.

@opensearch-trigger-bot opensearch-trigger-bot bot added stalled Issues that have stalled and removed stalled Issues that have stalled labels Nov 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants