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

[segment replication] decouple the rateLimiter of segrep and recovery #12959

Merged
merged 9 commits into from
Apr 14, 2024

Conversation

Ferrari248
Copy link
Contributor

@Ferrari248 Ferrari248 commented Mar 28, 2024

Description

add setting indices.replication.max_bytes_per_sec specially for segment replication, to decouple the rateLimiter of segment replication and recovery.

Related Issues

Resolves #12939

Check List

  • New functionality includes testing.
    • All tests pass
  • New functionality has been documented.
    • New functionality has javadoc added
  • Failing checks are inspected and point to the corresponding known issue(s) (See: Troubleshooting Failing Builds)
  • Commits are signed per the DCO using --signoff
  • Commit changes are listed out in CHANGELOG.md file (See: Changelog)
  • Public documentation issue/PR created

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.

… (12939)

add setting "segrep.max_bytes_per_sec"

Signed-off-by: maxliu <ly_chinese@163.com>
@github-actions github-actions bot added enhancement Enhancement or improvement to existing feature or request Indexing:Replication Issues and PRs related to core replication framework eg segrep Storage:Durability Issues and PRs related to the durability framework Storage:Remote labels Mar 28, 2024
Copy link
Contributor

❌ Gradle check result for 8b844fe: 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 cf5ecd1: SUCCESS

Copy link
Contributor

❕ Gradle check result for 25936fc: UNSTABLE

  • TEST FAILURES:
      1 org.opensearch.http.SearchRestCancellationIT.testAutomaticCancellationMultiSearchDuringFetchPhase

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 9f1e604: SUCCESS

@mch2
Copy link
Member

mch2 commented Apr 10, 2024

This LGTM @Ferrari248 just one last thing - given this is a user facing change I think we should add a changelog entry. Would you please update changelog.md here?

…opensearch-project#12939)

add setting "indices.replication.max_bytes_per_sec" which takes effect when not negative

Signed-off-by: maxliu <ly_chinese@163.com>

Adds change log

Signed-off-by: maxliu <ly_chinese@163.com>
Copy link
Contributor

✅ Gradle check result for 8c1a6ce: SUCCESS

@Ferrari248
Copy link
Contributor Author

Ferrari248 commented Apr 11, 2024

This LGTM @Ferrari248 just one last thing - given this is a user facing change I think we should add a changelog entry. Would you please update changelog.md here?

Thanks for review. Done.

Copy link
Contributor

❕ Gradle check result for 4f63511: UNSTABLE

  • TEST FAILURES:
      1 org.opensearch.remotestore.RemoteStoreStatsIT.testDownloadStatsCorrectnessSinglePrimaryMultipleReplicaShards

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 055765c: UNSTABLE

  • TEST FAILURES:
      1 org.opensearch.cluster.MinimumClusterManagerNodesIT.testThreeNodesNoClusterManagerBlock

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 47577b0: TIMEOUT

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: maxliu <ly_chinese@163.com>
Copy link
Contributor

✅ Gradle check result for fedc06c: SUCCESS

@mch2
Copy link
Member

mch2 commented Apr 12, 2024

added docs issue - opensearch-project/documentation-website#6948

@mch2 mch2 added backport 2.x Backport to 2.x branch documentation pending Tracks issues which have PRs merged but documentation changes pending labels Apr 12, 2024
@mch2 mch2 merged commit 6bc04b4 into opensearch-project:main Apr 14, 2024
46 of 53 checks passed
opensearch-trigger-bot bot pushed a commit that referenced this pull request Apr 14, 2024
…#12959)

* [segment replication] decouple the rateLimiter of segrep and recovery (12939)

add setting "segrep.max_bytes_per_sec"

Signed-off-by: maxliu <ly_chinese@163.com>

* [segment replication] decouple the rateLimiter of segrep and recovery (12939)

use setting "indices.replication.max_bytes_per_sec" if enable "indices.replication.use_individual_rate_limiter"

Signed-off-by: maxliu <ly_chinese@163.com>

* [segment replication] decouple the rateLimiter of segrep and recovery (12939)

setting "indices.replication.max_bytes_per_sec" takes effect when not negative

Signed-off-by: maxliu <ly_chinese@163.com>

* [segment replication] decouple the rateLimiter of segrep and recovery (#12939)

add setting "indices.replication.max_bytes_per_sec" which takes effect when not negative

Signed-off-by: maxliu <ly_chinese@163.com>

Adds change log

Signed-off-by: maxliu <ly_chinese@163.com>

---------

Signed-off-by: maxliu <ly_chinese@163.com>
(cherry picked from commit 6bc04b4)
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
mch2 pushed a commit that referenced this pull request Apr 15, 2024
…#12959)

* [segment replication] decouple the rateLimiter of segrep and recovery (12939)

add setting "segrep.max_bytes_per_sec"

Signed-off-by: maxliu <ly_chinese@163.com>

* [segment replication] decouple the rateLimiter of segrep and recovery (12939)

use setting "indices.replication.max_bytes_per_sec" if enable "indices.replication.use_individual_rate_limiter"

Signed-off-by: maxliu <ly_chinese@163.com>

* [segment replication] decouple the rateLimiter of segrep and recovery (12939)

setting "indices.replication.max_bytes_per_sec" takes effect when not negative

Signed-off-by: maxliu <ly_chinese@163.com>

* [segment replication] decouple the rateLimiter of segrep and recovery (#12939)

add setting "indices.replication.max_bytes_per_sec" which takes effect when not negative

Signed-off-by: maxliu <ly_chinese@163.com>

Adds change log

Signed-off-by: maxliu <ly_chinese@163.com>

---------

Signed-off-by: maxliu <ly_chinese@163.com>
(cherry picked from commit 6bc04b4)
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
mch2 added a commit that referenced this pull request Apr 15, 2024
…ep and recovery (#13181)

* [segment replication] decouple the rateLimiter of segrep and recovery (#12959)

* [segment replication] decouple the rateLimiter of segrep and recovery (12939)

add setting "segrep.max_bytes_per_sec"

Signed-off-by: maxliu <ly_chinese@163.com>

* [segment replication] decouple the rateLimiter of segrep and recovery (12939)

use setting "indices.replication.max_bytes_per_sec" if enable "indices.replication.use_individual_rate_limiter"

Signed-off-by: maxliu <ly_chinese@163.com>

* [segment replication] decouple the rateLimiter of segrep and recovery (12939)

setting "indices.replication.max_bytes_per_sec" takes effect when not negative

Signed-off-by: maxliu <ly_chinese@163.com>

* [segment replication] decouple the rateLimiter of segrep and recovery (#12939)

add setting "indices.replication.max_bytes_per_sec" which takes effect when not negative

Signed-off-by: maxliu <ly_chinese@163.com>

Adds change log

Signed-off-by: maxliu <ly_chinese@163.com>

---------

Signed-off-by: maxliu <ly_chinese@163.com>
(cherry picked from commit 6bc04b4)
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>

* Add back public API in RecoverySettings to 2.x

Signed-off-by: Marc Handalian <marc.handalian@gmail.com>

---------

Signed-off-by: maxliu <ly_chinese@163.com>
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Signed-off-by: Marc Handalian <marc.handalian@gmail.com>
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Co-authored-by: Marc Handalian <marc.handalian@gmail.com>
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 documentation pending Tracks issues which have PRs merged but documentation changes pending enhancement Enhancement or improvement to existing feature or request Indexing:Replication Issues and PRs related to core replication framework eg segrep Storage:Durability Issues and PRs related to the durability framework Storage:Remote
Projects
Status: ✅ Done
Development

Successfully merging this pull request may close these issues.

[Segment Replication] consider to decouple the rateLimiter of segrep and recovery
4 participants