feat: introduce a configurable checkpoint seeder (none or chaser) #100
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Docs will be done once this gets a green light. |
alexeyzimarev
approved these changes
Aug 24, 2024
yreynhout
force-pushed
the
checkpoint-seeder
branch
from
865d8c6 to
5951b25
Compare
alexeyzimarev
approved these changes
Aug 26, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added: a seeding capability for checkpoints on the startup of the replicator. It will only attempt to seed (1) if there is no stored checkpoint and (2) if there is something to seed with. If not, it will fall back to the current
ICheckpointStorebehavior, usually starting fromPosition.Start. Currently there's either the option to not seed (none) or to seed from achaser.chkfile (chaser). The rationale is that, if you mount the backup a server or cluster was restored from, thechaser.chkfile contains the position to resume replication from, thus acting as the seed of a checkpoint store. This change is currently only useful for ESDB to ESDB replication.