kvserver: defer snapshot scratch cleanup to Store.Start#171293
Merged
Conversation
Contributor
|
😎 Merged directly without going through the merge queue, as the queue was empty and the PR was up to date with the target branch - details. |
Member
pav-kv
approved these changes
Jun 2, 2026
Move sstSnapshotStorage.Clear() till after LoadAndReconcileReplicas (the future WAG-replay site). With separated engines, WAG replay can reference files in the scratch directory, so the cleanup must run after replay can consume them. Clear() still runs before Transport.ListenIncomingRaftMessages, so no in-flight scratch directory is at risk. Release note: None Epic: None
Contributor
Author
|
TFTR! /trunk merge |
This file contains hidden or 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
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.
Move sstSnapshotStorage.Clear() till after
LoadAndReconcileReplicas (the future WAG-replay site). With separated engines, WAG replay can reference files in the scratch directory, so the cleanup must run after replay can consume them.
Clear() still runs before Transport.ListenIncomingRaftMessages, so no in-flight scratch directory is at risk.
Release note: None
Epic: None