Streaming snapshot checkpoint in Tsavorite #824
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.
StreamingSnapshot
is a new checkpoint type that yields a stream of (mostly but not all distinct) key-value pairs that correspond to a consistent snapshot (versionv
) of the database. This can be used to create a checkpoint of the user's preferred format, or directly streamed to replicas, etc. To recover, the user needs to simply iterate over this stream in order, performing a sequence of upserts, and this will restore the consistentv
version (state) of the database.Treating this iterator as a checkpoint allows users to pair it with AOF replay to get exactly once processing semantics (TBD).
Current implementation makes the mutable region temporarily read-only, similar to a snapshot checkpoint. However, this can be optimized to avoid the copy-on-write in future, by making the update threads write out the old version
v
before updating it tov+1
in place.