fix(core): Delete binary data parent folder when pruning executions #11790
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.
Summary
When deleting binary data for executions in file-system mode, we should delete the entire executions folder, because when we only delete
binary_data
folder, the empty executions folders still take up inodes on the filesystem.Over time these empty folders accumulate enough to exhaust available inodes on the volume.
Context
Review / Merge checklist
release/backport
(if the PR is an urgent fix that needs to be backported)