Skip to content

Auto Force Merge Manager #18046

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

Closed
wants to merge 0 commits into from

Conversation

Harsh-87
Copy link

@Harsh-87 Harsh-87 commented Apr 23, 2025

Description

Added AutoForceMergeManager : Manages automatic force merge operations for indices in OpenSearch. This component monitors and triggers force merge on primary shards based on their translog age and system conditions. It ensures optimal segment counts while respecting node resources and health constraints. Force merge operations are executed with configurable delays to prevent system overload.

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.

Copy link
Contributor

❌ Gradle check result for 1cfef1b: 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 c84261d: 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 f474b01: 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 b1d70e8: 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

@ajaymovva ajaymovva left a comment

Choose a reason for hiding this comment

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

Thanks for the changes. Please include a link to the relevant issue or RFC in the pull request. This will provide necessary context for everyone reviewing the feature

Copy link
Contributor

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

@Harsh-87 Harsh-87 requested review from jed326 and a team as code owners April 30, 2025 10:20
Copy link
Contributor

❌ Gradle check result for 6073e45: 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 8c034b4: 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 fd401d3: 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?

@Harsh-87 Harsh-87 changed the title Config, Node and Shard Validations added Auto Force Merge Manager May 1, 2025
Copy link
Contributor

github-actions bot commented May 2, 2025

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

@Harsh-87 Harsh-87 requested a review from peternied as a code owner May 7, 2025 07:12
@Harsh-87 Harsh-87 closed this May 7, 2025
@Harsh-87 Harsh-87 mentioned this pull request May 7, 2025
3 tasks
@Harsh-87 Harsh-87 deleted the autoforcemerge branch May 12, 2025 10:35
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.

4 participants