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] Missing a request orchestrator to process replication events. #3112

Closed
Tracked by #2355
mch2 opened this issue Apr 29, 2022 · 0 comments · Fixed by #3439
Closed
Tracked by #2355

[Segment Replication] Missing a request orchestrator to process replication events. #3112

mch2 opened this issue Apr 29, 2022 · 0 comments · Fixed by #3439
Assignees

Comments

@mch2
Copy link
Member

mch2 commented Apr 29, 2022

Similar to PeerRecoveryTargetService that is used during peer recovery, Segment Replication needs a service class to orchestrate replication events for all shards on a node. This allows us to receive a new checkpoint and start a new replication event in a separate thread.

This is similar to the SegmentReplicationReplicaService class implemented in feature branch but. needs to be revisited and PR'd to main.

Similar to PeerRecoveryTargetService, replication events will need a target class implementation that is kicked off to start the event. Refactoring here would open the door for a SegmentReplicationTarget implementation that can be invoked from the service.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant