Automate build cache cleanup in orchestrator #253
+516
−38
Conversation
This file contains 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.
Description
Build cache cleanup automation is based on the percentage of free disk space. When the total disk usage reaches
90%, the oldest item in the cache is evicted. This is checked every second.File deletion (Close) is delayed by
60 secondsto prevent race conditions with exposed slices, pending data fetches, or data uploads. If the data scheduled for eviction is requested during this time, the eviction is canceled.Tests
There are automated tests for basic usage. I've done also manual testing by running
make mockas well as using SDK.