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

[DOC] Add documentation for separate Segment Replication rate limiting #6948

Closed
1 of 4 tasks
mch2 opened this issue Apr 12, 2024 · 4 comments · Fixed by #7048
Closed
1 of 4 tasks

[DOC] Add documentation for separate Segment Replication rate limiting #6948

mch2 opened this issue Apr 12, 2024 · 4 comments · Fixed by #7048
Assignees
Labels
3 - Done Issue is done/complete v2.14.0
Milestone

Comments

@mch2
Copy link
Member

mch2 commented Apr 12, 2024

What do you want to do?

  • Request a change to existing documentation
  • Add new documentation
  • Report a technical problem with the documentation
  • Other

Tell us about your request. Provide a summary of the request and all versions that are affected.
With this PR we will be adding an additional index setting indices.replication.max_bytes_per_sec to control the max bytes per second for node-node segment replication.

This page should be updated to reflect this new setting.

I am thinking:

indices.replication.max_bytes_per_sec (String): Limits the total inbound and outbound replication traffic for each node. This applies to segment replication between nodes. Default is tied to the set value of indices.recovery.max_bytes_per_sec, which is by default 40mb. If you set the replication traffic value to less than or equal to 0mb, rate limiting will be disabled, which causes replication data to be transferred at the highest possible rate.

What other resources are available? Provide links to related issues, POCs, steps for testing, etc.

@hdhalter
Copy link
Contributor

Thanks, @mch2 ! I assume we are targeting 2.14?

@hdhalter hdhalter added 1 - Backlog - DEV Developer assigned to issue is responsible for creating PR. and removed untriaged labels Apr 12, 2024
@mch2
Copy link
Member Author

mch2 commented Apr 14, 2024

@hdhalter Yup this will be introduced starting 2.14. Thanks

@hdhalter hdhalter added this to the v2.14 milestone Apr 14, 2024
@hdhalter
Copy link
Contributor

Hi @mch2 , what is your ETA for producing the doc PR? To meet entrance criteria, the PR must be open and in review by 4/30. Thanks!

@mch2
Copy link
Member Author

mch2 commented Apr 25, 2024

Hi @mch2 , what is your ETA for producing the doc PR? To meet entrance criteria, the PR must be open and in review by 4/30. Thanks!

Will get this up today thanks for the heads up!

@hdhalter hdhalter added 2 - In progress Issue/PR: The issue or PR is in progress. and removed 1 - Backlog - DEV Developer assigned to issue is responsible for creating PR. labels Apr 29, 2024
@hdhalter hdhalter added 3 - Done Issue is done/complete and removed 2 - In progress Issue/PR: The issue or PR is in progress. labels Apr 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3 - Done Issue is done/complete v2.14.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants