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] Review existing snapshot and restore compatibility with SegRep #3695

Closed
dreamer-89 opened this issue Jun 24, 2022 · 3 comments
Assignees
Labels
enhancement Enhancement or improvement to existing feature or request Indexing & Search

Comments

@dreamer-89
Copy link
Member

dreamer-89 commented Jun 24, 2022

As part of this issue, we want to identify if SegRep enabled cluster have any issues with snapshot and recovery. In case there are issues, identify changes needed to make it compatible. Concretely, we want to test snapshot/restore in below scenarios:

  1. Snapshot & restore on segrep disabled cluster.
  2. Snapshot & restore on segrep enabled cluster.
  3. Snapshot on docrep cluster and restore on segrep cluster & vice-versa.

Segment Replication

@dreamer-89 dreamer-89 added enhancement Enhancement or improvement to existing feature or request untriaged labels Jun 24, 2022
@dreamer-89 dreamer-89 self-assigned this Jun 24, 2022
@dreamer-89
Copy link
Member Author

dreamer-89 commented Jul 6, 2022

Wrote segment replication integration tests for snapshot in commit below
dreamer-89@91aa303. The initial integration tests shows that segment replication works with snapshot & restore feature. Added tests as mentioned in the issue description.

This is built on top of commit mch2@f996894. Waiting for a working segrep changes before trying out a manual snapshot test.

@Rishikesh1159
Copy link
Member

Rishikesh1159 commented Sep 16, 2022

With opensearch 2.3 version, we have Segment replication feature as an experimental release. I have tested the latest 2.3 version with all the 3 above mentioned testing scenarios. The snapshot and restore process is compatible with segment replication in all above mentioned scenarios. I used this doc to understand the process of snapshot and restore. Here are the steps I used to test these:

Steps to Verify:
-> First I run a single node cluster.
-> Then I registered a repository (locally [file system] not on s3/remote store) for storing snapshots
-> Then I created an index of size 18gb with replicas and segment replication enabled.
-> Then I took a snapshot of the cluster.
-> Then I deleted the index.
-> Then I restore cluster from snapshot and i see deleted index came up again with segment replication enabled and entire 18gb size.
-> Later I tested in different scenarios by creating a segment replication enabled index and taking snapshot of cluster. Then I deleted the index and while restoring I restored the index with document replication enabled and entire process was successful. Similar result with vice-versa scenarios.

@dreamer-89
Copy link
Member Author

dreamer-89 commented Sep 16, 2022

Snapshot & Restore changes are tested manually as mentioned in last comment. Integration tests are also added via #3993 to ensure snapshot/restore flow is not broken with segrep enabled.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Enhancement or improvement to existing feature or request Indexing & Search
Projects
None yet
Development

No branches or pull requests

3 participants