Expand scope of DurabilityProvider
to include snapshotting
#3295
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.
The
DurabilityProvider
trait was introduced to enable theHostController
to procure an alternativeDurability
impl from an external source.It is also useful to be able to instantiate a
SnapshotWorker
externally, in order to subscribe to snapshot creation events without access to theRelationalDB
instance it is operating on.At a later stage, we may also use it to control the snapshot frequency externally.
This patch thus reframes the trait as
PersistenceProvider
, whose job is to provide persistence-related services.Also separates snapshot creation and compression of older snapshots, and adds instrumentation to gather timing information for both.
Description of Changes
Re-submit of #3281 (reverted by #3293), with only the intended changes.
Expected complexity level and risk
1.5
Testing
No functional changes.