Document how temporary storage is used #1801
Merged
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.
When working on an issue-at-scale recently with a community user, I became concerned that maybe our software was consuming too much temporary storage on their system. This made me realize that we're overdue to reveal this information so users have a chance of doing this kind of debug on our own, or at least I could easily point them to an article if this comes up again. As it turns out, I think this info grafts nicely onto the existing Filesystem Paths article.
While running tests to write this content, I actually found multiple bugs where we're not currently cleaning up after ourselves the way we should (brimdata/brimcap#136, brimdata/zed#2983). Normally in these situations I'd confess these issues in the article, link to them, and then update the article once they get fixed. However, I have high hopes we'll get these fixed pretty quick, so for now I've kept it tidy.