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] Handle new ReplicationCheckpoints when received by replicas. #3110

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

Comments

@mch2
Copy link
Member

mch2 commented Apr 29, 2022

With issue #2927, ReplicationCheckpoints will be received and passed to IndexShards for processing.

Shards should receive these requests and:

  1. Compute the existing checkpoint and validate against the requested checkpoint. Dedupe incoming requests & ensure we are processing one checkpoint at a time.
  2. Process the checkpoint by kicking off a new replication event.
  3. Handle replication failure.

A version of this logic is implemented in the feature branch here, but needs to be revisited and PR'd to main. This is an effort to cut the merge into smaller digestible chunks. This can trigger an empty start method inside of a service class.

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

No branches or pull requests

2 participants