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]Segment replication added consideration #4984

Closed
1 of 4 tasks
Poojita-Raj opened this issue Sep 7, 2023 · 0 comments · Fixed by #5037
Closed
1 of 4 tasks

[DOC]Segment replication added consideration #4984

Poojita-Raj opened this issue Sep 7, 2023 · 0 comments · Fixed by #5037
Assignees
Labels
3 - Done Issue is done/complete v2.10.0
Milestone

Comments

@Poojita-Raj
Copy link
Contributor

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.
https://opensearch.org/docs/latest/tuning-your-cluster/availability-and-recovery/segment-replication/index/#considerations
Under segment replication considerations, we want to add another consideration

7.  For segment replication -  Get, MultiGet, TermVector and MultiTermVector requests serve strong reads by routing requests to the primary shards. In a read heavy cluster (especially with listed request types), it is advisable to set the `realtime` parameter in these requests to `false`.

What other resources are available? Provide links to related issues, POCs, steps for testing, etc.
opensearch-project/OpenSearch#8536
opensearch-project/OpenSearch#9212
opensearch-project/OpenSearch#9563

@Naarcha-AWS Naarcha-AWS added 1 - Backlog Issue: The issue is unassigned or assigned but not started and removed untriaged labels Sep 7, 2023
@Naarcha-AWS Naarcha-AWS self-assigned this Sep 7, 2023
@Naarcha-AWS Naarcha-AWS added this to the v2.10 milestone Sep 7, 2023
@Naarcha-AWS Naarcha-AWS added 2 - In progress Issue/PR: The issue or PR is in progress. and removed 1 - Backlog Issue: The issue is unassigned or assigned but not started labels Sep 12, 2023
@hdhalter hdhalter added 3 - Done Issue is done/complete and removed 2 - In progress Issue/PR: The issue or PR is in progress. labels Sep 19, 2023
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.10.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants