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

Cache index shard limit to optimise ShardLimitsAllocationDecider #14962

Merged
merged 11 commits into from
Jul 29, 2024

Conversation

imRishN
Copy link
Member

@imRishN imRishN commented Jul 24, 2024

Description

As described in the issue, with large number of shards, ShardsLimitAllocationDecider spends lots of time parsing settings. As a part of this PR, we are caching the setting value to optimise the decider run time.


Benchmark Before Changes

Benchmark                                              (indicesNodes)  Mode  Cnt       Score       Error  Units
RerouteBenchmark.measureShardAllocationEmptyCluster      10000|  500|  avgt    3  839663.255 ± 48190.442  ms/op

Benchmark After Changes

Benchmark                                              (indicesNodes)  Mode  Cnt       Score       Error  Units
RerouteBenchmark.measureShardAllocationEmptyCluster      10000|  500|  avgt    3  755228.219 ± 41246.861  ms/op

Percentage improvement while assigning 200k shards - 10.05%


Related Issues

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

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.

Copy link
Contributor

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

imRishN added 2 commits July 25, 2024 02:34
Signed-off-by: Rishab Nahata <[email protected]>
Signed-off-by: Rishab Nahata <[email protected]>
Signed-off-by: Rishab Nahata <[email protected]>
Copy link
Contributor

❌ Gradle check result for ec6ce0b: 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 fe6e5d9: 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 4ed2164: 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: Rishab Nahata <[email protected]>
Copy link
Contributor

❌ Gradle check result for 439bce2: 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: Rishab Nahata <[email protected]>
Copy link
Contributor

❌ Gradle check result for 818a902: 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: Rishab Nahata <[email protected]>
Copy link
Contributor

❌ Gradle check result for 2f3b3e1: 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 a93f11d: 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
Contributor

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

codecov bot commented Jul 27, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 71.86%. Comparing base (1fe58b5) to head (b937cfc).
Report is 6 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff              @@
##               main   #14962      +/-   ##
============================================
+ Coverage     71.78%   71.86%   +0.07%     
- Complexity    62694    62752      +58     
============================================
  Files          5160     5161       +1     
  Lines        294211   294363     +152     
  Branches      42553    42577      +24     
============================================
+ Hits         211212   211540     +328     
+ Misses        65599    65403     -196     
- Partials      17400    17420      +20     

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

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

✅ Gradle check result for b937cfc: SUCCESS

@Bukhtawar Bukhtawar merged commit 122f3f0 into opensearch-project:main Jul 29, 2024
31 of 32 checks passed
@Bukhtawar Bukhtawar added the backport 2.x Backport to 2.x branch label Jul 29, 2024
opensearch-trigger-bot bot pushed a commit that referenced this pull request Jul 29, 2024
)

* Cache index shard limit per node

Signed-off-by: Rishab Nahata <[email protected]>
(cherry picked from commit 122f3f0)
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
dblock pushed a commit that referenced this pull request Aug 7, 2024
) (#15000)

* Cache index shard limit per node


(cherry picked from commit 122f3f0)

Signed-off-by: Rishab Nahata <[email protected]>
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
harshavamsi pushed a commit to harshavamsi/OpenSearch that referenced this pull request Aug 20, 2024
wdongyu pushed a commit to wdongyu/OpenSearch that referenced this pull request Aug 22, 2024
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 skip-changelog
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants