Skip to content

Reduce runtime of PitMultiNodeIT by 6 minutes #18167

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
merged 1 commit into from
May 1, 2025

Conversation

andrross
Copy link
Member

This commit reduces the runtime of the test from over 6 minutes to about 10 seconds. The current code attempts to do a flush after a node has dropped, resulting in waiting on the replication timeout of 1 minute. The change here is to ensure the flush happens before any nodes are stopped.

Check List

  • Functionality includes testing.

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.

This commit reduces the runtime of the test from over 6 minutes to about
10 seconds. The current code attempts to do a flush after a node has
dropped, resulting in waiting on the [replication timeout][1] of 1
minute. The change here is to ensure the flush happens before any nodes
are stopped.

[1]: https://github.com/opensearch-project/OpenSearch/blob/7977446398fda5d553f39e2db32a395e917b9c78/server/src/main/java/org/opensearch/action/support/replication/ReplicationRequest.java#L64

Signed-off-by: Andrew Ross <[email protected]>
Copy link
Contributor

❌ Gradle check result for 2fecfbf: 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 2fecfbf: 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 May 1, 2025

❌ Gradle check result for 2fecfbf: 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 May 1, 2025

✅ Gradle check result for 2fecfbf: SUCCESS

Copy link

codecov bot commented May 1, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 72.52%. Comparing base (a6724d3) to head (2fecfbf).
Report is 14 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff              @@
##               main   #18167      +/-   ##
============================================
- Coverage     72.53%   72.52%   -0.02%     
- Complexity    67207    67250      +43     
============================================
  Files          5476     5476              
  Lines        310436   310437       +1     
  Branches      45121    45121              
============================================
- Hits         225179   225142      -37     
- Misses        66894    67002     +108     
+ Partials      18363    18293      -70     

☔ 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.

Copy link
Contributor

@deshsidd deshsidd left a comment

Choose a reason for hiding this comment

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

LGTM. Nice fix!

@mch2 mch2 merged commit 2ba6aac into opensearch-project:main May 1, 2025
54 checks passed
@andrross andrross deleted the speed-up-pit-test branch May 1, 2025 20:35
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