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

[Backport 2.17] Schedule reroute after allocator timed out #15687

Merged
merged 2 commits into from
Sep 5, 2024

Conversation

imRishN
Copy link
Member

@imRishN imRishN commented Sep 4, 2024

  • Schedule reroute after allocator timed out

Description

Backport #15565

Related Issues

Resolves #[Issue number to be closed when this PR is merged]

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.

* Schedule reroute after allocator timed out

Signed-off-by: Rishab Nahata <[email protected]>
@imRishN imRishN changed the title [Backport 2.17] Schedule reroute after allocator timed out (#15565) [Backport 2.17] Schedule reroute after allocator timed out Sep 4, 2024
Copy link
Contributor

github-actions bot commented Sep 4, 2024

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

Copy link
Contributor

github-actions bot commented Sep 4, 2024

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

Signed-off-by: Rishab Nahata <[email protected]>
Copy link
Contributor

github-actions bot commented Sep 4, 2024

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

Copy link
Contributor

github-actions bot commented Sep 5, 2024

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

github-actions bot commented Sep 5, 2024

❕ Gradle check result for c1f6471: 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 5, 2024

Codecov Report

Attention: Patch coverage is 78.12500% with 7 lines in your changes missing coverage. Please review.

Project coverage is 71.71%. Comparing base (ccae165) to head (c1f6471).
Report is 18 commits behind head on 2.17.

Files with missing lines Patch % Lines
...pensearch/gateway/ShardsBatchGatewayAllocator.java 76.47% 0 Missing and 4 partials ⚠️
.../allocation/allocator/BalancedShardsAllocator.java 81.81% 0 Missing and 2 partials ⚠️
.../routing/allocation/allocator/ShardsAllocator.java 0.00% 1 Missing ⚠️
Additional details and impacted files
@@             Coverage Diff              @@
##               2.17   #15687      +/-   ##
============================================
- Coverage     71.73%   71.71%   -0.03%     
+ Complexity    64250    64244       -6     
============================================
  Files          5251     5252       +1     
  Lines        300362   300391      +29     
  Branches      43704    43709       +5     
============================================
- Hits         215471   215413      -58     
- Misses        66908    66983      +75     
- Partials      17983    17995      +12     

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants