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.

Sign up for GitHub

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

Jump to bottom

[Segment Replication] Trigger segment copy after initial recovery. #4036

Closed
Tracked by #2194
mch2 opened this issue Jul 28, 2022 · 1 comment
Closed
Tracked by #2194

[Segment Replication] Trigger segment copy after initial recovery. #4036

mch2 opened this issue Jul 28, 2022 · 1 comment
Labels
distributed framework enhancement Enhancement or improvement to existing feature or request

Comments

@mch2
Copy link
Member

mch2 commented Jul 28, 2022

Coming from - #3483

After recovery completes today replicas will be in-sync in that all docs are made durable on replica shards, but ops copied will not be searchable. Replicas will require an additional refresh cycle to catch up to primaries. We can mitigate this by triggering a segrep copy event after recovery completes, before marking the shard as active.
@mch2 mch2 added enhancement Enhancement or improvement to existing feature or request distributed framework labels Jul 28, 2022
@mch2 mch2 mentioned this issue Jul 28, 2022
Closed
31 tasks
@mch2
Copy link
Member Author

mch2 commented Jan 6, 2023

Closing as completed - #5332

@mch2 mch2 closed this as completed Jan 6, 2023
@anasalkouz anasalkouz moved this from Todo to Done in Segment Replication Feb 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
distributed framework enhancement Enhancement or improvement to existing feature or request
Projects
Segment Replication
Status: Done
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mch2