materialize: delete superseded blobs (quota blowout fix) - #421
Merged
Conversation
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.
Root cause of the frozen store: every sweep writes a new content-hash blob (dataAsOf changes each time) and the 24h TTL let ~4300 orphan blobs pile up overnight, blowing the Upstash 256MB quota; every write then failed http 400 while the worker looked alive. publishSnapshot now deletes the previously-pointed blob right after the swap, TTL drops to 2h as safety net. The full DB has been purged of ocb:mat:* (4345 keys) and the worker rebuilt.