-
Notifications
You must be signed in to change notification settings - Fork 505
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
Add segment replication + remote store GA information #5037
Conversation
Signed-off-by: Naarcha-AWS <naarcha@amazon.com>
Signed-off-by: Naarcha-AWS <naarcha@amazon.com>
@dreamer-89: This PR is ready for your review. Let me know if there is anything I missed. |
_tuning-your-cluster/availability-and-recovery/segment-replication/index.md
Outdated
Show resolved
Hide resolved
_tuning-your-cluster/availability-and-recovery/segment-replication/index.md
Outdated
Show resolved
Hide resolved
_tuning-your-cluster/availability-and-recovery/segment-replication/index.md
Outdated
Show resolved
Hide resolved
_tuning-your-cluster/availability-and-recovery/segment-replication/index.md
Outdated
Show resolved
Hide resolved
_tuning-your-cluster/availability-and-recovery/segment-replication/index.md
Outdated
Show resolved
Hide resolved
_tuning-your-cluster/availability-and-recovery/segment-replication/index.md
Outdated
Show resolved
Hide resolved
_tuning-your-cluster/availability-and-recovery/segment-replication/index.md
Outdated
Show resolved
Hide resolved
_tuning-your-cluster/availability-and-recovery/segment-replication/index.md
Outdated
Show resolved
Hide resolved
Signed-off-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com>
Signed-off-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com>
_tuning-your-cluster/availability-and-recovery/segment-replication/index.md
Outdated
Show resolved
Hide resolved
_tuning-your-cluster/availability-and-recovery/segment-replication/index.md
Outdated
Show resolved
Hide resolved
_tuning-your-cluster/availability-and-recovery/segment-replication/index.md
Outdated
Show resolved
Hide resolved
_tuning-your-cluster/availability-and-recovery/segment-replication/index.md
Outdated
Show resolved
Hide resolved
…tion/index.md Co-authored-by: Suraj Singh <surajrider@gmail.com> Signed-off-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com>
_tuning-your-cluster/availability-and-recovery/segment-replication/index.md
Outdated
Show resolved
Hide resolved
_tuning-your-cluster/availability-and-recovery/segment-replication/index.md
Outdated
Show resolved
Hide resolved
_tuning-your-cluster/availability-and-recovery/segment-replication/index.md
Outdated
Show resolved
Hide resolved
_tuning-your-cluster/availability-and-recovery/segment-replication/index.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Bukhtawar Khan <bukhtawar7152@gmail.com> Signed-off-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com>
_tuning-your-cluster/availability-and-recovery/segment-replication/index.md
Outdated
Show resolved
Hide resolved
_tuning-your-cluster/availability-and-recovery/segment-replication/index.md
Outdated
Show resolved
Hide resolved
Signed-off-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com>
Signed-off-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good but we need to reference a consistent name (either remote-backed storage or remote store).
_tuning-your-cluster/availability-and-recovery/remote-store/remote-segment-backpressure.md
Show resolved
Hide resolved
_tuning-your-cluster/availability-and-recovery/segment-replication/index.md
Outdated
Show resolved
Hide resolved
_tuning-your-cluster/availability-and-recovery/segment-replication/index.md
Outdated
Show resolved
Hide resolved
_tuning-your-cluster/availability-and-recovery/segment-replication/index.md
Outdated
Show resolved
Hide resolved
_tuning-your-cluster/availability-and-recovery/segment-replication/index.md
Outdated
Show resolved
Hide resolved
_tuning-your-cluster/availability-and-recovery/segment-replication/index.md
Outdated
Show resolved
Hide resolved
Co-authored-by: kolchfa-aws <105444904+kolchfa-aws@users.noreply.github.com> Signed-off-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com>
Signed-off-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Naarcha-AWS Please see my comments and changes and let me know if you have any questions. Thanks!
_tuning-your-cluster/availability-and-recovery/segment-replication/index.md
Outdated
Show resolved
Hide resolved
_tuning-your-cluster/availability-and-recovery/segment-replication/index.md
Outdated
Show resolved
Hide resolved
As of OpenSearch 2.10, you can use two methods for segment replication: | ||
|
||
- With **remote-backed storage**, a persistent storage solution: The primary shard sends segment files to the remote-backed storage and the replica shards source the copy from the same store. For more information about using a remote-backed storage, see [Remote-backed storage]({{site.url}}{{site.baseurl}}/tuning-your-cluster/availability-and-recovery/remote-store/index/#segment-replication-and-remote-backed-storage). | ||
- Without remote-backed storage: The primary shard sends segment files directly to the replica shards using node-to-node communication. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we call the second method what it is, as opposed to what it isn't? Node-to-node replication?
_tuning-your-cluster/availability-and-recovery/segment-replication/index.md
Outdated
Show resolved
Hide resolved
_tuning-your-cluster/availability-and-recovery/segment-replication/index.md
Outdated
Show resolved
Hide resolved
_tuning-your-cluster/availability-and-recovery/segment-replication/index.md
Outdated
Show resolved
Hide resolved
_tuning-your-cluster/availability-and-recovery/segment-replication/index.md
Outdated
Show resolved
Hide resolved
_tuning-your-cluster/availability-and-recovery/segment-replication/index.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Nathan Bower <nbower@amazon.com> Signed-off-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com>
* Add segment replication + remote store GA information Signed-off-by: Naarcha-AWS <naarcha@amazon.com> * Add introduction labels Signed-off-by: Naarcha-AWS <naarcha@amazon.com> * Apply suggestions from code review Signed-off-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com> * Apply suggestions from code review Signed-off-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com> * Update _tuning-your-cluster/availability-and-recovery/segment-replication/index.md Co-authored-by: Suraj Singh <surajrider@gmail.com> Signed-off-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com> * Apply suggestions from code review Co-authored-by: Bukhtawar Khan <bukhtawar7152@gmail.com> Signed-off-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com> * Apply suggestions from code review Signed-off-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com> * Update index.md Signed-off-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com> * Apply suggestions from code review Co-authored-by: kolchfa-aws <105444904+kolchfa-aws@users.noreply.github.com> Signed-off-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com> * Replace Remote Store with Remote Backed Storage Signed-off-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com> * Apply suggestions from code review Co-authored-by: Nathan Bower <nbower@amazon.com> Signed-off-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com> --------- Signed-off-by: Naarcha-AWS <naarcha@amazon.com> Signed-off-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com> Co-authored-by: Suraj Singh <surajrider@gmail.com> Co-authored-by: Bukhtawar Khan <bukhtawar7152@gmail.com> Co-authored-by: kolchfa-aws <105444904+kolchfa-aws@users.noreply.github.com> Co-authored-by: Nathan Bower <nbower@amazon.com>
…ject#5037) * Add segment replication + remote store GA information Signed-off-by: Naarcha-AWS <naarcha@amazon.com> * Add introduction labels Signed-off-by: Naarcha-AWS <naarcha@amazon.com> * Apply suggestions from code review Signed-off-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com> * Apply suggestions from code review Signed-off-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com> * Update _tuning-your-cluster/availability-and-recovery/segment-replication/index.md Co-authored-by: Suraj Singh <surajrider@gmail.com> Signed-off-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com> * Apply suggestions from code review Co-authored-by: Bukhtawar Khan <bukhtawar7152@gmail.com> Signed-off-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com> * Apply suggestions from code review Signed-off-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com> * Update index.md Signed-off-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com> * Apply suggestions from code review Co-authored-by: kolchfa-aws <105444904+kolchfa-aws@users.noreply.github.com> Signed-off-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com> * Replace Remote Store with Remote Backed Storage Signed-off-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com> * Apply suggestions from code review Co-authored-by: Nathan Bower <nbower@amazon.com> Signed-off-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com> --------- Signed-off-by: Naarcha-AWS <naarcha@amazon.com> Signed-off-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com> Co-authored-by: Suraj Singh <surajrider@gmail.com> Co-authored-by: Bukhtawar Khan <bukhtawar7152@gmail.com> Co-authored-by: kolchfa-aws <105444904+kolchfa-aws@users.noreply.github.com> Co-authored-by: Nathan Bower <nbower@amazon.com>
* Add segment replication + remote store GA information Signed-off-by: Naarcha-AWS <naarcha@amazon.com> * Add introduction labels Signed-off-by: Naarcha-AWS <naarcha@amazon.com> * Apply suggestions from code review Signed-off-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com> * Apply suggestions from code review Signed-off-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com> * Update _tuning-your-cluster/availability-and-recovery/segment-replication/index.md Co-authored-by: Suraj Singh <surajrider@gmail.com> Signed-off-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com> * Apply suggestions from code review Co-authored-by: Bukhtawar Khan <bukhtawar7152@gmail.com> Signed-off-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com> * Apply suggestions from code review Signed-off-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com> * Update index.md Signed-off-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com> * Apply suggestions from code review Co-authored-by: kolchfa-aws <105444904+kolchfa-aws@users.noreply.github.com> Signed-off-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com> * Replace Remote Store with Remote Backed Storage Signed-off-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com> * Apply suggestions from code review Co-authored-by: Nathan Bower <nbower@amazon.com> Signed-off-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com> --------- Signed-off-by: Naarcha-AWS <naarcha@amazon.com> Signed-off-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com> Co-authored-by: Suraj Singh <surajrider@gmail.com> Co-authored-by: Bukhtawar Khan <bukhtawar7152@gmail.com> Co-authored-by: kolchfa-aws <105444904+kolchfa-aws@users.noreply.github.com> Co-authored-by: Nathan Bower <nbower@amazon.com>
Checklist
For more information on following Developer Certificate of Origin and signing off your commits, please check here.