docs(storage): describe the discard policy that actually runs - #384
Merged
Conversation
The latency-safe contract is nopassdown, not passdown. Document its bounded loop-file space trade-off and remove the reference to a private evidence file that does not exist.
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
1 participant
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.
Correct the public maintenance contract to match the measured
nopassdownpolicy: local thin-extent reuse avoids multi-second job IO stalls, while the bounded sparse loop file may retain host blocks. Remove the nonexistent private evidence-file reference. Fullmake verifypasses.